In the wix.targets (and wix2010.targets) file(s) you will find properties such as WixTargetsPath (normally set in your WIXPROJ file), WixTasksPath, LuxTargetsPath, and LuxTasksPath (also, from wix.ca.targets add WixCATargetsPath to this list). You will want to generate and supply each of these properties for your entire build/solution somewhere convenient.
Regarding passing those object-type files between different builds of the toolset: you can run into problems since the content (and schema) of these files can vary between builds and there isn't a strong validation to ensure that they aren't passed between builds. Thus, yes, you may have unexpected things happen if you share those files between tools from different builds of the toolset. Regarding VS integration, I was referring to the way that Votive creates files and maintains projects and the fact that using WiX from an enlistment instead of "installing" it means that Votive isn't available to VS (as a GUI). During builds you only care about MSBuild accessing WiX, so VS doesn't need Votive then, but during design Votive is used by VS if you use VS to build your projects/solutions (I rarely use VS myself while I use MSBuild a lot). -----Original Message----- From: little.forest [mailto:little.for...@ymail.com] Sent: Wednesday, August 11, 2010 11:52 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] .NET 4 and Wix 3.5 Thanks Blair. I'm glad to know the binaries which is nice. Speaking of "do the configuration yourself", what kind of configuration do I need to do? Is there any document for it? For "and you need to avoidpassing things like WIXOUTs, WIXOBJs, WIXPDBs, WIXLIBs, etc. from one buildof WiX to another ", Do you mean we should avoid mixing using those files between Wix 3.0 and 3.5? Also, at the end, you said "and things like VS integration still require just oneversion at-a-time, but ... ", what do you mean "but"? Thanks. ________________________________ From: Blair <os...@live.com> To: General discussion for Windows Installer XML toolset. <wix-users@lists.sourceforge.net> Sent: Mon, August 9, 2010 5:34:20 PM Subject: Re: [WiX-users] .NET 4 and Wix 3.5 <dumb-mouse-pointer/> As I was saying before being so rudely interrupted, you have to do your own configuration for your build platform, etc. yourself, and you need to avoid passing things like WIXOUTs, WIXOBJs, WIXPDBs, WIXLIBs, etc. from one build of WiX to another, and things like VS integration still require just one version at-a-time, but ... -----Original Message----- From: Blair [mailto:os...@live.com] Sent: Monday, August 09, 2010 5:31 PM To: 'General discussion for Windows Installer XML toolset.' Subject: RE: [WiX-users] .NET 4 and Wix 3.5 That's what the binaries.zip is for: to add WiX to a version-control to avoid installing it to a build system. You have to do the configuration yourself, but -----Original Message----- From: little.forest [mailto:little.for...@ymail.com] Sent: Monday, August 09, 2010 4:44 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] .NET 4 and Wix 3.5 We're migrating our app to use .NET 4.0. We'll need to detect and install .NET 4.0. We're using Wix 3.0. From this post(http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/NetFxExte nsion-and-NET-4-td4969906.html#a4969906 ), it seems we need to move to Wix 3.5. But I tried to install Wix 3.5 - it replaced the version 3.0. This is a problem: in our build server, we installed Wix 3.0 already. If 3.5 replaces 3.0, our old builds cannot be built because they can't find the 3.0 compiler(the path thing). Is there a way that 3.0 and 3.5 co-exist in one machine? If yes, how to do it? If not, is it possible to install 3.5 in one machine, and then copy the candle/light stuff over to some other machine and use it? In another word, Wix 3.5 must be installed to run(needs some registry or system stuff be there)? Or it can run like a portable application? Thanks! ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
