Hi
We create separate 32 and 64 bit EXE installers from a set of 32 and 64 bit MSM packages. The MSM packages contain various components which are either unique to the installer or shared by several product installers, for example the exe for the application being installed (unique), documents for the application (unique), various shared libraries used by the application (common), etc. We generate separate 32 and 64 bit installers as this fits more easily in our automated build process so ideally we want to stick with this.
The problem I am having is that we want to be able to allow both a 32 bit and 64 bit install of the application onto a Windows 7 64 bit machine simultaneously. All the MSM and top level EXE installers have unique GUIDs so there is no issues in having the side by side installations, in addition all files are stored in unique directories, for example bin/bin64 and lib/lib64. Previously this all worked fine as we had a launch batch file for the 32 or 64 bit application which determined the appropriate 32 or 64 bit executable to run and set up the paths appropriately. However as our application requires administrator privileges to do certain operations, and now under Windows 7 this is a lot more involved than simply ensuring the user running the application is in the local administrator group, we have moved to embedding a UAC privilege request manifest into the application. As such the batch file approach does not work due to paths not being inherited, etc. to a privileged application, so I now need to add registry keys in
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\<our app.exe>
for the 64 bit application and
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\App Paths\<our app.exe>
for the 32 bit application with the (Default) and Path keys set to the appropriate architecture dependent executable and directories respectively.
So I added these registry keys to the MSM which contains the application. For both the 32 bit and 64 bit MSM projects I simply added the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\<our app.exe> keys as I assumed the installer would sort out appropriately that on a 64 bit install that was the correct path and on a 32 bit it should be redirected to the Wow6432Node version.
However when I install the 32 bit installer on the Windows 7 64 bit machine I first get the (Default) and Path keys for the 32 bit application written to both registry trees (32 and 64 bit), but when I install the 64 bit installer it also writes to both, hence breaking the 32 bit install in Wow6432Node as the path is not invalid.
I found a tutorial on 32/64 bit registry keys http://www.advancedinstaller.com/user-g ... istry.html but that seemed to be specific to the case of a mixed 32/64 bit installer. However I tried various suggestions from it including marking the Organisation containing the (Default) and Path keys as a 64-bit Component in the 64 bit MSM. This did not seem to have any effect. I then tried the option to Disable Registry Reflection again on the 64 bit MSM thinking from the description that this would stop it writing through to the Wow6432Node keys as well. This however also failed.
I am now out of ideas on this one and would appreciate any help.
Thanks
FOLLOW US
Get the latest news in Application Packaging