Hi folks,
I have a Build VM where I have installed VS2012 but have NOT installed WIX
3.9
I have rebuilt WIX 3.9 with some changes to the bootstrapper (I added some
pre requisite checks that our product requires) (If I install WIX 3.9 and
replace the binaries built and is good, but we do not want
Hello,
I've created two WiX setups as well as a Bootstrapper that contains both
.msi files inside its Chain. Now I want to build both setups and the BA with
TFS Build.
The build itself is successful, I've already moved the WiX sources to TFS
and changed the WiX paths to a relative location
On 13/03/2013 20:13, jeamis wrote:
So how do I enlist to the Mercurial repository? All I want to do is
compile burn. I want to confirm our static analysis and debugging.
Any direction is appreciated.
Clone https://hg.codeplex.com/wix :
hg clone https://hg.codeplex.com/wix -b wix38
To
On 19/03/2013 12:31, Bruce Cran wrote:
Clone https://hg.codeplex.com/wix :
hg clone https://hg.codeplex.com/wix -b wix38
Sorry ignore most of that - those instructions are for WiX 3.8 not 3.6.
To get 3.6 you just need to use -b wix36 when cloning and follow the
instructions in the
Ok, I see that on http://wix.codeplex.com/releases/view/93929 there is a zip
file that contains source. What is needed to build the wix 3.6 toolkit?
Can I build it using DevStudio 2010? Is the source complete?
I tried to open the wix.sln (which my machine says it is 2010 sln file, but
it
You need to enlist in the Mercurial repository to build. The sources.zip is
availble for debugging purposes (along with the pdbs.zip) it is not
buildable. To build wix36, you use make.bat. It requires lots of stuff
installed on your machine to build correctly.
On Wed, Mar 13, 2013 at 11:07 AM,
Thanks Rob,
So how do I enlist to the Mercurial repository? All I want to do is
compile burn. I want to confirm our static analysis and debugging.
Any direction is appreciated.
-Jon
-
- jon
--
View this message in context:
Rob,
* [property] Target framework changed to Microsoft .NET Framework 2.0. -
NOT SOLVED
* [property] Read-only property dir.hhw cannot be overwritten. - SOLVED
- by removing read-only=true from source code
* [property] Read-only property hhw-found cannot be overwritten. - SOLVED
- by
I am facing same issue i.e. need to build wixstdba.vcxproj project. If any
one got its solution then please let me know the solution.
-
jaczjill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/building-Wix-tp7474266p7580340.html
Sent from the
The WiX v3.6 buid is (unfortunately) wired to build from the beginning and
all the way through. You do have to have the whole environment (lots of
stuff to install) to get there.
On Thu, Sep 6, 2012 at 6:58 AM, jaczjill jaczj...@gmail.com wrote:
I am facing same issue i.e. need to build
As we now have a 3.6 RC0, I wanted to take another stab at burn. When I
attempt to build on a clean machine (Win 7 x64) with just VS2010, the
6.1 and 7.1 SDK, and NAnt I keep getting errors like:
[exec] Microsoft (R) Build Engine Version 3.5.30729.5420
[exec] [Microsoft .NET
hello
i'm having problem building wix :
i have installed all the required prerequisites (or at their equivalent
for Visual 2010)
i basically just would like to build wixstdba, (it requires the balutil.lib
)
- building any project in ext.sln (or in the wix solution) shows
The XsdGen task was
was enough for me.
Hope this helps.
Neil
-Original Message-
From: jean claude klodjan [mailto:jcklod...@gmail.com]
Sent: 17 April 2012 18:27
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] building Wix
hello
i'm having problem building wix :
i have installed all the required
OK, Brian I am back again with a new question. Been Digging around the wix
code. :)
Now I have tried out Project harvester and the problem is I cannot get in
all the dll's included with the project. Basically we have multiple
projects in the solution. So I tried to use the
Satellites
Hey Brian,
Am I understanding you correctly when you say you have dependency .dlls
listed in the project itself? If that is the case you could create a
separate call to heat.exe to get those files as individuals. Unfortunately
the only other way I know how to do this would be to use the
Thanks for the answer Brian.
Yes, its very basic and ugly for some of our apps. I am working on that as
well.
What would be ideal is if you could just specify the .sln file and then heat
automagically fetched all the structure plus reference dlls. That would
be the dream..Perhaps version 4.0 of
Hello Brian, thanks for your response below. It solved just about
everything for me. Now I have a problem with the heat output:
File Id=filECAD2FA36BABE7788C7D38952DE30E56 KeyPath=yes
Source=SourceDir\
So I tried to do this here:
Adding this:
HeatDirectory
PreprocessorVariable=$(var.MyVar)
.../
Hey Brian,
Which version of heat.exe are you using? Is it this weeks drop? Second, if
you could show more or your source wixproj that would be great. Also, the
PreprocessorVariable takes only var.MyVar not $(var.MyVar).
Do you know about the VSProject harvestor extension? This might work for
Thanks Brian I am using the latest drop of wix.
Brian, no I didn't know about the project harvester. That is basically what
I am trying to do. Is there any info on how to use it anywhere?
On Apr 20, 2009 5:38 PM, Brian Rogers rogers.br...@gmail.com wrote:
Hey Brian,
Which version of heat.exe
Hello all (I posted this to the wrong list on friday(wix-users-request))
Rob pointed out to me that there was a way to use heattasks:
http://stackoverflow.com/questions/710687/best-way-to-create-a-wix-fragment-file-based-on-user-defined-directories-to-be-us,but
I have not been able to get
Hey Brian,
Try the below.
PropertyGroup
Configuration Condition= '$(Configuration)' == ''
Debug/Configuration
OutputNamemsbuild.heatfile/OutputName
OutputTypePackage/OutputType
WixToolPath*Pass via the command line*/WixToolPath
Culturesen-us/Cultures
Thank you, it's working!
Bob Arnson-6 wrote:
Dmitry Ponomarenko wrote:
I am not sure how I can specify this property in the project file - there
is
no such option over UI.
Could you please provide me with an example for the project file with
setting the property?
You'll have to
Dmitry Ponomarenko wrote:
I am not sure how I can specify this property in the project file - there is
no such option over UI.
Could you please provide me with an example for the project file with
setting the property?
You'll have to do it in a text editor since it's not exposed in the
Hello Bob,
I am not sure how I can specify this property in the project file - there is
no such option over UI.
Could you please provide me with an example for the project file with
setting the property?
Thanks,
Dmitry
Bob Arnson-6 wrote:
Dmitry Ponomarenko wrote:
I am in trouble with
Hello All,
I am in trouble with building my WiX solution using NAnt and MSBuild task on a
server which is running under Windows 2003 x64.
NAnt task is simple:
exec program=msbuild.exe basedir=${ProspX.netFrameworkPath}
workingdir=${wc.branchPath} resultproperty=setup.WiX.result
Dmitry Ponomarenko wrote:
I am in trouble with building my WiX solution using NAnt and MSBuild task on
a server which is running under Windows 2003 x64.
NAnt will run as a 64-bit process on an x64 machine; for compatibility,
the WiX tools are marked as x86 and NAnt won't be able to load
Vidya Kukke wrote:
One last thing, I was wondering how come if it has not been localized in
japanese I get warnings only for a few strings? Is it that these are new and
have been introduced only in 3.0 but the rest of the strings were in 2.0 and
are available for use as-is in 3.0?
The
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Building Wix for ja-JP
Hi,
I am using Wix v3 (3.0.4805). I have a requirement to build ja-JP version of
our installer. However when I change the culture to build to ja-JP (via VS 2008
project settings) I am getting the following errors
clarify this?
Regards,
Vidya
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Friday, January 16, 2009 9:04 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building Wix for ja-JP
Vidya Kukke wrote:
Is there any plan to do
January 2009 19:20
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building Wix for ja-JP
:-).
One last thing, I was wondering how come if it has not been localized in
japanese I get warnings only for a few strings? Is it that these are new
and have been
Hi,
I am using Wix v3 (3.0.4805). I have a requirement to build ja-JP version of
our installer. However when I change the culture to build to ja-JP (via VS 2008
project settings) I am getting the following errors:-
C:\delivery\Dev\wix30\src\ext\UtilExtension\wixlib\UtilExtension.wxs(207,0):
It does not appear that anyone has provided localization for those messages,
yet.
-Original Message-
From: Vidya Kukke [mailto:vku...@windows.microsoft.com]
Sent: Thursday, January 15, 2009 15:35
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Building Wix for ja-JP
Hi,
I am
for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building Wix for ja-JP
It does not appear that anyone has provided localization for those messages,
yet.
-Original Message-
From: Vidya Kukke [mailto:vku...@windows.microsoft.com]
Sent: Thursday, January 15, 2009 15:35
To: wix-users
If it messes up the build yes.
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2008 22:33
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX from CVS
Should I raise that as a bug?
-Original
You are of course correct but I am such a total convert to
SVN that everything in CVS looks so antiquated. I use CVS
tags in another project but have never have the enthusiasm to
understand the command line, in SVN I do everything via the
TortiseSVN interface and I assumed TortiseCVS would be
Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
From: John Hall [mailto:[EMAIL PROTECTED]
Sent: Fri 24/10/2008 10:00
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
You are of course correct but I am
It sounds like you know a bit about CVS, do you know if it is
possible to view what has change since you last did a
checkout in CVS or TortoiseCVS? I can see how to do it on a
file by file basis but not the whole folder.
Neil,
On the commandline, you can do 'cvs -n update', which shows you
]
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Wed 22/10/2008 23:40
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
Can we get the appropriate details added to the help file? Detailed bugs would
be fantastic
: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2008 03:48
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
I will raise bugs for the instructions. Do you also want them for missing
files? I have seen posts mentioning the limited
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
The instructions should say, Sync files from CVS. The source.zip is
just provided for quick look up during debugging on a machine that you
might not have CVS source on. If you're going to be working
... there are just other things that *don't*
work that take priority. smile/
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2008 10:17
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
Rob
I
:42
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
1. This was my fault in the past, and things are better now (or so I've
heard smile/).
2. CVS should be better than sources.zip. If not, it'd be good to know
what's busted in CVS.
3. It would
Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 23, 2008 10:54
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
1. I'll give the CVS branch a go and see how I get on.
2. My point was that the zip file is a working
: 23 October 2008 19:06
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
2. That's a good point. There are no labels in CVS. I'll think about
it in the future. It'd be a good feature to have.
4. If the source control is working then I have
Following on from my other posts I thought I'd try and build WIX from
CVS, the first problem I encountered is that the test folder does
export from CVS. These are the command lines I am using:
cvs.exe -d:pserver:[EMAIL PROTECTED]:/cvsroot/wix login
cvs.exe -z3 -d:pserver:[EMAIL
Neil Sleightholm wrote:
2. I wouldn't bother in CVS they are as good as useless. The tools I
have seem to only show labels on files and not the whole project and I
have never found a way of doing a get by label - even VSS can do that!
If by labels you mean tags, then they aren't useless at
be the same but it isn't.
Neil
-Original Message-
From: Braden McDaniel [mailto:[EMAIL PROTECTED]
Sent: 23 October 2008 19:46
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX
Neil Sleightholm wrote:
2. I wouldn't bother in CVS they are as good
Neil Sleightholm wrote:
Following on from my other posts I thought I'd try and build WIX from
CVS, the first problem I encountered is that the test folder does
export from CVS. These are the command lines I am using:
I don't think it exists in CVS. It's not visible from
Should I raise that as a bug?
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 24 October 2008 01:37
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX from CVS
Neil Sleightholm wrote:
Following on from my other posts I
If anyone is interested in building WiX from the source I have written a
blog that details the bits that aren't in the help file:
http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix-build-mach
ine.html.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] mailto:[EMAIL
Can we get the appropriate details added to the help file? Detailed bugs would
be fantastic.
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 15:08
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users
Sean Farrow wrote:
Wherecan I get the required version of nant? I carn't find it on the
nant sourceforge page.
http://nant.sourceforge.net/nightly/
--
sig://boB
http://joyofsetup.com/
-
This SF.Net email is
Thanks bob.
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 30 September 2008 06:36
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building WiX v3
Sean Farrow wrote:
Wherecan I get the required version of nant? I carn't find
Hi:
Wherecan I get the required version of nant? I carn't find it on the
nant sourceforge page.
Cheers
Sean.
-Original Message-
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: 28 September 2008 22:58
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users
Hi:
I am looking at buildingWiX v3, I'm currently working on some internal
extensions and I'd like to understand the build process. To build WiX,
do I need the .net framework 1.1? or just 2.0/3.0/3.5.
Any help apreciated.
Sean.
Sean Farrow wrote:
I am looking at buildingWiX v3, I'm currently working on some internal
extensions and I'd like to understand the build process. To build WiX,
do I need the .net framework 1.1? or just 2.0/3.0/3.5.
You don't need .NET 1.1; you do need 3.5 and either VS2008 or the
Windows
Bob Arnson wrote:
Christopher Painter wrote:
Yes, I would volunteer for such an effort. I know I've been told to
`put up or shut up` before but I never helped out because I'm not the
strongest C# application developer. However in the build / release
role I'm very comfortable and I feel
I have a hard time believing it would take months to complete. I make a living
ripping apart and refactoring .NET solutions that were stored in other SCC/WIT
systems and checking them into TFS proper. A project the size of WiX wouldn't
take me more then a few days to migrate.
I'd
Christopher Painter wrote:
Oh come on... I'm sure a company as big as MSFT can come up with a
little bit of hosting space for open space projects.
I'm sure. But it's weeks/months of effort so we can make building from
source .zips easier? Bad ROI. Codeplex still doesn't have mailing lists,
Luke Bakken wrote:
It would be a smaller effort to get the current build to be
bulletproof for someone doing a CVS checkout. I've already done this
to some degree as I have a local vendor branch of WiX to which I've
applied several important patches for our installers (the patches have
been
Christopher Painter wrote:
Yes, I would volunteer for such an effort. I know I've been told to
`put up or shut up` before but I never helped out because I'm not the
strongest C# application developer. However in the build / release
role I'm very comfortable and I feel that it's something
On Feb 12, 2008 1:21 PM, Bob Arnson [EMAIL PROTECTED] wrote:
Christopher Painter wrote:
Oh come on... I'm sure a company as big as MSFT can come up with a
little bit of hosting space for open space projects.
I'm sure. But it's weeks/months of effort so we can make building from
source
Yes, I would volunteer for such an effort. I know I've been told to `put up or
shut up` before but I never helped out because I'm not the strongest C#
application developer. However in the build / release role I'm very
comfortable and I feel that it's something I could do to help the cause.
Oh come on... I'm sure a company as big as MSFT can come up with a little bit
of hosting space for open space projects.
Just go to the CodePlex group and say `We are the poster child for Microsoft
Open Source and we are using SourceForge instead of CodePlex because they have
feature
Frédéric Viollet wrote:
-I finally found these files in the binary distribution. I tried from
the weekly release sources after copying the files above, I got the
following error:
71 errors, all about missing references... because Nant.Core could not
be found.
:)
Is there a way to
Frédéric Viollet wrote:
-I tried from a CVS checkout, I got the following error:
c:\temp\wix_cvs\wix.build(64,4):
Build file 'C:\temp\wix_cvs\tests\vstests\vstests.build' does not exist.
Yeah, sorry, I just noticed this problem last weekend. You can comment
out every include of .build files
Bob Arnson a écrit :
Frédéric Viollet wrote:
C:\temp\wix-3.0.2925.0-sourcesmake.bat ship
Please try a weekly release from http://wix.sourceforge.net/releases/
or a CVS checkout.
Hi Bob,
Thanks again for replying.
-I tried from a CVS checkout, I got the following error:
Is it really not possible to include all files in the source
distribution so that building wix can be automated in a production
environment?
*why* do you need to build WIX in a production environment?
/Simon
-
This
Why not just go to CodePlex?The TFS/MSBuild model kills the CVS/NAnt model,
IMHO. I know you guys said you had some issues building unmanaged code but
surely it can't be that bad.
Bob Arnson [EMAIL PROTECTED] wrote:
Frédéric Viollet wrote:
-I tried from a CVS checkout, I got the
Frédéric Viollet wrote:
C:\temp\wix-3.0.2925.0-sourcesmake.bat ship
Please try a weekly release from http://wix.sourceforge.net/releases/ or
a CVS checkout.
--
sig://boB
http://joyofsetup.com/
-
This SF.net email
Hi everyone,
I'm encoutering some problems while trying to build Wix v3 with nant
I get the following error message:
C:\temp\wix-3.0.2925.0-sourcesmake.bat ship
NAnt 0.85 (Build 0.85.2478.0; release; 14/10/2006)
Copyright (C) 2001-2006 Gerry Shaw
http://nant.sourceforge.net
Buildfile:
Thanks for these notes. Moving to CLR v2.0 was an interesting struggle
and I don't think we have all of our build dependencies worked out. The
AssemblyInfo.cs is totally one of those files that I've messed up. I've
been struggling with the freaking keys for a while (keeping the private
I needed to create a custom WiX build (based on 3.0.3617.0) to fix twobugs
(1591591 1653864) that were plaguing us. We have been using WiXfor over a
year on our project and other than those two bugs we havebeen really happy with
the project.
I have worked with other open source
To answer your question about building the WiX toolset. You
cant do it by just downloading VS. We designed the build process
to work from freely available tools. There was some early criticism of the
WiX project being a way to force people to buy Visual Studio.
So, now you just need to
74 matches
Mail list logo
