The same forms application is referenced by both installers. The reference "Full Path" reflects the build configurations. The PROD reference full path is bin/x86/prodBuildConfig/forms.exe and the TEST reference full path is bin/x86/testBuildConfig/forms.exe. All build configurations set the forms app platform to x86, including prodBuildConfig and testBuildConfig.
Robert -----Original Message----- From: Blair Murri [mailto:os...@live.com] Sent: Wednesday, 6 November 2013 3:55 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] platform x86 vs AnyCPU problems WiX installation projects don't "produce" any applications (except for bundles). They just package them. Could it be that the two installers are capturing two differing instances of the application that happen to be tagged differently WRT bitness? Possibly the path to the application is computed differently? Never really heard of that happening. WiX installers don't alter their payloads, so it isn't anything overt that can do that sort of thing. -Blair > From: rob...@softdev.net > To: wix-users@lists.sourceforge.net > Date: Wed, 6 Nov 2013 03:45:12 +0000 > Subject: [WiX-users] platform x86 vs AnyCPU problems > > I have a Visual Studio 2012 Forms Application with 2 WiX installers - > TEST and PROD. Because of a 3rd party dll, I need to restrict the > output to x86 for all machines. My development machine is x64. In > order to achieve this, > > - all Build configurations in the solution have the Forms application > set to x86 (there are many class libraries, web apps, consoles, > services in the solution) > - In the Wix xml installer project, I have compiler parameters set to "-arch > x86" for "all configurations" > - in the Product.wxs packages element I have set Platform="x86" > > The PROD installer successfully produces a 32 bit app. I can easily tell this > using the Telerik JustDecompile utility. > The TEST installer fails and produces "Any CPU" .exe > > - the Components.wxs files for both PROD and TEST are identical > - the Product.wxs only differ in GUIDs and descriptions > > I've tried everything and cannot see what the difference is between the 2 > installers and why one produces a x86 .exe and the other AnyCPU. So far I've > spent about 4 hours... and counting... > > Robert > ---------------------------------------------------------------------- > -------- November Webinars for C, C++, Fortran Developers Accelerate > application performance with scalable programming models. Explore > techniques for threading, error checking, porting, and tuning. Get the > most from the latest Intel processors and coprocessors. See abstracts > and register > http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.c > lktrk _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users