Then either make 2 packages & bootstrap them together so the correct one installs automatically for the user or don't use Windows Installer.
Palbinder Sandher Software Platform Engineer T: +44 (0) 141 945 8500 F: +44 (0) 141 945 8501 http://www.iesve.com **Design, Simulate + Innovate with the <Virtual Environment>** Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456 Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 0SP Email Disclaimer -----Original Message----- From: Marius Bancila [mailto:marius.banc...@gmail.com] Sent: 09 February 2012 21:06 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] registry search overridden when "Program Files" encountered Here is the situation: I have this application that is available both as 32-bit and 64-bit. Now I'm building an installer for an SDK for the app, consisting on documents, .NET samples and other files. These are all platform independent. However, they (some of them at least) must be installed in the same place with the app (the reason is not important for the discussion). I don't want to make two packages and tell the customers "if you have 32-bit app, run this setup, if you have the 64-bit app run the other". I want to make it simple for customers, and so I want a single setup to be able to handle all these. On Thu, Feb 9, 2012 at 7:52 PM, Pally Sandher <pally.sand...@iesve.com>wrote: > ProgramFilesFolder = "Program Files (x86)" -> > http://msdn.microsoft.com/en-us/library/aa370881.aspx > ProgramFiles64Folder<http://msdn.microsoft.com/en-us/library/aa370881.aspx%0AProgramFiles64Folder>= > "Program Files" -> > http://msdn.microsoft.com/en-us/library/aa370880.aspx > > You can't write to 64-bit locations from 32-bit processes such as msiexec > running your x86 package. Either make a x64 package or live with it. > > Palbinder Sandher > Software Platform Engineer > T:+44 (0) 141 945 8500 > F:+44 (0) 141 945 8501 > http://www.iesve.com > > **Design, Simulate + Innovate with the <Virtual Environment>** > Integrated Environmental Solutions Limited. Registered in Scotland No. > SC151456 > Registered Office - Helix Building, West Of Scotland Science Park, Glasgow > G20 0SP > Email Disclaimer > > > -----Original Message----- > From: Marius Bancila [mailto:marius.banc...@gmail.com] > Sent: 09 February 2012 13:32 > To: wix-users@lists.sourceforge.net > Subject: [WiX-users] registry search overridden when "Program Files" > encountered > > Hi, > > I have the following problem installing to a path read from the registry. > I'm using WIX 3.5 (and currently testing on a Win7 64-bit). > > I'm doing a registry search like this: > > <Property Id="APPINSTALLDIR"> > <RegistrySearch Id='TheAppPath' Type='raw' > Root='HKCU' Key='Software\MyApplication' Name='Path' /> > </Property> > > Then I use it like this: > > <Directory Id='TARGETDIR' Name='SourceDir'> > <Directory Id='ProgramFilesFolder' Name='PFiles'> > <Directory Id='MyCompany' Name='MyCompany'> > <Directory Id="APPINSTALLDIR" Name="MyProduct"> > <!-- etc. etc. --> > </Directory> > </Directory> > </Directory> > </Directory> > > I'm expected to install in the path read from Registry, or if it's missing > under (32-bit) Program Files\MyCompany\MyProduct. > I must mention that the target platform for the project is x86. > > Everything works fine when the Path value does not start with "C:\Program > Files" (for intance C:\Program Files\MyCompany\MyProduct). In this case > somehow the property is always set to "C:\Program Files (x86)\etcetc" (i.e. > C:\Program Files (x86)\MyCompany\MyProduct). Obviously I don't want that. I > guess the Windows Installer thinks he knows better and replaces it, but I > want to install to that exact location. If for instance Path is "C:\my > Program Files\etcetc\" then there is no problem. > > Has anyone ran into this problem and knows the cause? I need to find a > solution for this. > > Thank you very much, > Marius Bancila > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
