Not using Burn. My installers create an msi file in the file system. When that is copied to and run on a client machine, a windows forms application is created in the Program files (x86)/[Companyname]/[ProgramName] directory. Inside this directory there are several dll's, config files and a formsapp.exe. This is the .exe I'm referring to. Because of third party dll's, I need this to be x86, which is the problem. Between my 2 installers, one works and the other creates a Any CPU forms.exe, which fails because of the third party dlls.
-----Original Message----- From: Nicolás Alvarez [mailto:nicolas.alva...@gmail.com] Sent: Friday, 8 November 2013 2:34 PM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] platform x86 vs AnyCPU problems Are you using a bootstrapper like Burn and referring to the installer .exe, or are you referring to an .exe file your installer installs? -- Nicolás 2013/11/7 Robert Clancy <rob...@softdev.net>: > I have 2 distinct Wix XML Installer projects in the solution. The solution > build configuration determines which is built. I have a PROD build > configuration which includes building the WiXProd installer and a TEST build > config which includes building the WisTEST installer. Both PRODbuildconfig > and TESTbuildconfig also include the same Forms application which is set to > x86. The 2 WiX installers are also set to x86 in the solution build > configuarion. On top of that, I have set -arch x86 in their project > properties and added Platform="x86" to their package elements. One installer > creates a x86 .exe and the other creates an Any CPU .exe!!! > > -----Original Message----- > From: John H Bergman (XPedient) [mailto:john.berg...@xpdnt.com] > Sent: Friday, 8 November 2013 4:23 AM > To: General discussion about the WiX toolset. > Subject: Re: [WiX-users] platform x86 vs AnyCPU problems > > I'm interested in this as well. I hadn't considered this because we have > different binaries (same name, different directories); but you are right, > this would be nice to be able to use a single Wix Project for both; right now > I use the same Wix source using linked (add as reference) files. > > -----Original Message----- > From: Blair Murri [mailto:os...@live.com] > Sent: Thursday, November 7, 2013 7:37 AM > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] platform x86 vs AnyCPU problems > > Without seeing more of your MSBuild code (like your project references) it’s > hard to do more than pure conjecture, or even to repro. > > > > > > > Blair > > > > > > From: Robert Clancy > Sent: Wednesday, November 06, 2013 3:37 PM > To: General discussion for Windows Installer XML toolset. > > > > > > Thank you Phil for the suggestion, but unfortunately it didn't work. The > wixproj files are identical except for guids and descriptions. The OutputName > elements contain just the application names. There was a difference in > ItemGroup order which I changed to make the ordering identical, closed, > reloaded, exited, rebuilt - still "Any CPU" for the TEST installer output > .exe. The text "Any CPU" doesn't appear anywhere in either of the wixproj > files. > > This element is identical in both: > > <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|x86' > "> > <OutputPath>bin\$(Configuration)\</OutputPath> > <IntermediateOutputPath>obj\$(Configuration)\</IntermediateOutputPath> > <CompilerAdditionalOptions>-arch x86</CompilerAdditionalOptions> > </PropertyGroup> > > - Robert > > -----Original Message----- > From: Phill Hogland [mailto:phogl...@rimage.com] > Sent: Thursday, 7 November 2013 1:02 AM > To: wix-users@lists.sourceforge.net > Subject: Re: [WiX-users] platform x86 vs AnyCPU problems > > If I understand the issue, I would go to each of the two project files > (Prod.*proj and TEST.*proj), right click on each file and select 'Unload', > then right click and select Edit Prod.wixproj (or TEST.wixproj). Then > compare the working to the non-working file. It sounds like your OutputName > element in the 'global' (top most) PropertyGroup has been overwritten to 'Any > CPU' (which is a possible value VS might pass into $(Platform) MSBuild > property). > > I was working on a similar issue in my build process recently, because I have > a mixture of wix, C#, and C++ projects which require different platform > specifications. In the course of doing that I came across the chm (and > Candle /? output) which indicates that Package/@Platform (and -d:Platform) is > discouraged (or deprecated) and that -arch is prefered. So I added the > InstallerPlatform element to my project files and set it to x64 in the > situation where I needed the -arch=x64. > > When you finish editing a .*proj file you need to close it and then right > click and 'reload' it. I have also found that if you change any .target or > .prop file that is imported by the project, you really need to close the > solution and re-open the solution (so I often do that anyway just to make > sure that I know that my new changes have been loaded prior to testing them). > If you do not close and reopen the solution, imported targets stay in memory > and do not reflect changes made after they were first loaded (at least that > is the behavior of VS2010). > > ------------------------------------------------------------------------------ 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
