I think it depends on the requirements of your application. For me I have six different driver projects which I author from a single project (each) and build either as a x64 or a x86 MSI package in my automated build script. I use the same UpgradeCode for the two packages. In my Burn bundle I chain the two packages (with other packages) and condition the MsiPackage/@InstallCondition with VersionNT64 or NOT VersionNT64. This assures that only the driver native to the OS can be installed.
While I have not done this, from what I read in Bob's blog you can use multiple UpgradeCode to assure that other products are removed before a particular product is installed. http://www.joyofsetup.com/2008/09/07/hint-be-generous-with-upgrade-codes/ -- 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-tp7596280p7596282.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
