I’m building an installer that automatically selects which software to install based on the architecture (VersionNT64 condition on one feature, NOT VersionNT64 on the other), but there are a couple of registry keys that need to go in as well. If I turn on “64-Bit Component”, it will (apparently) write to the appropriate part of the registry, but that requires a flag in the installer info that prevents it from opening on a 32-bit machine. The component even has the VersionNT64 condition on it, so it wouldn’t even be used on a 32-bit machine, so is there another way around this? I have a couple of alternatives in mind (reset the flag after compile; custom action on a .reg file) but I’d prefer something more streamlined.
I’m building an installer that automatically selects which software to install based on the
Share
From what I know you can a component marked as a 64-bit one in a 32 bit package without preventing the package to work on x86 machines. Only if the package type is set to x64 it will stop working on x86 machines.