Another way would be to create a copy of the project using linked files that has a different project name (say with x86 in the name), and target the build to a different output directory.
Depending on the size of the assembly and what's in it, it's easy to do with the linked files; although it does require you to add the link if you add a new file; or add the resources directly to both because Microsoft doesn't pay attention to the directory structure of links (they all end up in the root namespace). What I ended up doing is creating a second .sln file that had the specific settings for the other platform, and then build that first, followed but the solution that has the wix projects. We end up with something like 25 installers and 15 merge modules to facilitate the various configurations and customer requirements. This works well when using TFSBuild (with the workflow-based build process template) in 2010. -----Original Message----- From: Michael Stoll [mailto:unwicht...@mistoll.de] Sent: Thursday, June 02, 2011 1:09 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] MSBuild project references and multiple platforms of the same components AFAIK this is not possible. I did something like that by modifiying the msbuild process using two 'msbuild' tasks (http://msdn.microsoft.com/en-us/library/z7f65y0d.aspx) for building the x64 and the x86 platform dependencies. Michael Am 02.06.2011 19:54, schrieb Randy Johnson: > Hi, > > I have a question about using MSBuild and including multiple platforms (i.e. > 32-bit and 64-bit) of the *same* component in an msi. Using Visual Studio I > can add a project references from my WIX project to any dependent project (C# > class library, etc.) and it will be built first. So for instance if I build > with the "x64" platform specified then it builds the x64 version of my > assembly before in build the WIX project. This is great for if you just want > one platform included. However what if you want to include both a 32-bit and > 64-bit versions of the same assembly in your .msi? Is it possible to add a > separate project reference for each configuration of a referenced project? Or > is there some other way to achieve what I want to do? Any help would be > really appreciated! > > FYI I am using Visual Studio 2010, and WIX v3.5. > > Thanks, > Randy > ---------------------------------------------------------------------- > -------- Simplify data backup and recovery for your virtual > environment with vRanger. > Installation's a snap, and flexible recovery options mean your data is > safe, secure and there when you need it. Discover what all the cheering's > about. > Get your free trial download today. > http://p.sf.net/sfu/quest-dev2dev2 > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
