Hi,
I just want the same EXE to be installed *as though* 32-bit on a 32-bit system, and as though 64-bit on a 64-bit system.
Since the EXE is not specific to a platform, it can be included in the common feature (the feature which is installed on both 32-bit and 64-bit systems).
It's also unclear what impact selecting "64-bit component" in the Organization tab has.
Based on this option Windows Installer determines if the resource is 32-bit or 64-bit and installs it in the appropriate location. Also, this option marks the package as 64-bit. Please note that this option does not affect the resource itself.
I understand that one must choose 64-bit for registry entries to avoid virtualization (Wow6432),
Please note that the
virtualization is not related to this (it is a Vista concept for legacy applications). A 64-bit system has two sets of locations:
- 32-bit locations for 32-bit packages and components
- 64-bit locations for 64-bit packages and components
If the component of your EXE was not marked as 64-bit, it would be installed in a 32-bit location ("Program Files" on a 32-bit system and "Program Files (x86)" on a 64-bit system). If it's marked as 64-bit it is installed in a 64-bit location ("Program Files").
Since you are using the custom Advanced Installer property, the installation folder is set automatically according to the platform type (a 32-bit folder for 32-bit systems and a 64-bit folder for 64-bit systems). This way you don't have to create two copies for the common files (one in the "Program Files" folder and one in the "Program Files 64" folder from "Files and Folders" page).
Basically, for your application you can use a mixed package with the EXE set to be installed on both platforms. If you use the Advanced Installer custom property, the EXE will be automatically installed in a 32-bit folder on a 32-bit machine and in a 64-bit folder on a 64-bit machine.
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging