I have two MSIs: one for 32bit and one for 64bit. They contain similar components.
32bit - contains only 32bit components 64bit - contains both 32bit and 64bit components To allow MajorUpgrades, when building the MSIs, the UpgradeCode for each MSI is different, unique, and static. The ProductCode changes with each build (via the '*' mechanism) and so does the ProductVersion. We have an automated build system. Therefore it is possible for a user to install both the 32bit and 64bit product on the target machine. I presume I can prevent this double install with Launch Conditions so that if the 64bit UpgradeCode is on the machine, hence, the 64bit version is installed, the 32bit MSI will fail with an explanatory message. A similar scenario will occur for the 32bit to 64bit scenario. Is there a better way to allow the installs to occur and have the 32bit replace the 64bit, and the 64bit to replace the 32bit? I would think though, it could be better to keep these mutually exclusive and force the user to uninstall the current bitness if they want to install a different bitness. What are the communities thoughts on this Friday? Thanks! -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-Prevent-32bit-and-64bit-MSIs-with-Different-UpgradeCodes-and-Dynamic-ProductCodes-from-Both-Bd-tp7596280.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
