You can edit that property (<DefineConstants>) in the property pages if
you're using Votive. Just right mouse click the project in Solution Explorer
and click "Properties." Alternatively, you can edit the .wixproj file
directly and add <DefineConstants>Name=Value;Name2=Value2</DefineConstants>
within an existing <PropertyGroup>. Make sense?
Justin
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Wednesday, February 07, 2007 11:00 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Wix 3.0 and Votive?
Sorry I'm kind of new to this. Is that the msbuild file for the specific
project correct? Is there a way to edit that in VS/TFS?
From: Cullen Waters [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 1:01 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?
What I did was set a property called <DefineConstants> in my MSBuild file.
Then, when candle is executed, the WixTasks convert that semicolon separated
list of variables into -d<name>=<value> when passed into the candle command
line. The only thing you might have to do is change the env. prefix to
var., if nant was setting an environment variable for you.
From: Scott Sam [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 07, 2007 8:58 AM
To: Cullen Waters; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?
Thanks, I've gotten the wxs files updated, and added them to the projects in
TFS. How do you handle the source path for the files being added to the
msi? Before I used a nant variable in the wix as part of the path. Is
there a similar way to do this using MSBuild? It looks like the path will
change based on whether or not it is a debug or release build.
From: Cullen Waters [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 01, 2007 1:54 PM
To: Scott Sam; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Wix 3.0 and Votive?
I just moved my whole team from v2 to v3.
In general, the update went really smoothly. You can use wixcop.exe to
update all of the xml for you. Wixcop doesn't, however remove shortnames,
which might cause you some headaches. I went through all my xml and
manually deleted all the short names.
What might cause you some extra work, depending on how you use v2, is that
v3 runs msi validation as part of light. We found a bunch of msival errors
in our MSIs when we went to v3, and it took some time to work through them.
This is a good thing, though, since you have essentially raised the quality
bar of your installers by doing this.
We use votive with VS Team Suite, and we haven't had any problems yet.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Sam
Sent: Thursday, February 01, 2007 10:47 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Wix 3.0 and Votive?
I was thinking of trying out votive. We are using Visual Studio Team
Edition for Developers with Team Foundation Server. We are also using WIX
v2 for the msi. I was wondering, is Wix v3 stable enough to use if we are
deploying our next version of our product in about 3-5 months. Has anyone
used votive with team foundation server? Are there any problems to be
expected when moving from wix v2 to wix v3?
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
