I have a bit of a problem. Since our client application is only 32 bit, I've run up against a challenge of adding some third party Merge Modules that have 64 bit components marked as such. I can't add them to my 32 Bit package without changing it to x64 so I thought I would Chain a 64 bit installer to place these.
For the most part, it works as the Merge Modules are configurable so when I pass my 32 bit INSTALLDIR to the chain, the components go where they need to go, almost.
There are some Common program files that should end up in the 64 bit Program Files\Common Files\MyFolder, but they end up in Program Files (x86)\Common Files\MyFolder.
If I run the chained installer standalone it appears OK so the thought was that running the 64 bit chained install from 32 bit process makes directories a hairy issue. Registry entries seem to be OK as, when chained, they go to the 64 bit hive as hoped.
So, I was hoping there was a way to set the desired Common Files directory in the 64 bit installer to avoid placement in the (x86) area. I tried setting the directory to [%CommonProgramFiles], but it still goes to the 32 bit area.
Any ideas on how I can get this stuff where it needs to be.
UPDATE: More details to the Common Files issue. Chaining my installer works as desired on XP 64, but does not work on Win 7 64. The common files end up in Program Files (x86) on that OS.
Am I running up against a security issue of some kind. My initial install is fired off by an Admin. Does that chained install not inherit the rights of the 'parent' or main install? I'm reaching.
Edited by Superfreak3, 20 June 2012 - 19:45.