Sorry about the formatting of the last post; somehow my mail client stripped out all the newlines. Let me try this again:
I'd think there must be a way to do this, but I haven't found one in the MSI docs or wix-users archives. I've got two existing installers for different products with different upgrade codes. I'd like to make a new installer which will be a major upgrade replacing both of them. That's easy, right? I just need one Upgrade element for each of the old upgrade codes so that RemoveExistingProducts will uninstall them. But my concern is that those old installers are already out there in the world, and I'd like them to refuse to install after the upgrade has run. The old installers do check for a newer version and refuse to install, but they're each checking different upgrade codes. As far as I can tell, I need my installer to publish multiple upgrade codes, but I can't see any supported way to do that in a single installer, since there's only one UpgradeCode property. The only solution I can imagine (aside from awful kludges like hacking the registry directly or using MsiDoAction to run the PublishProduct action multiple times) is to create separate MSI files to install empty "version 127" products of the old upgrade codes, and install those alongside my new installer. Since concurrent installation is frowned upon, I assume this would require some sort of bootstrapper/chainer. Is there some better way to accomplish this, or is a chainer the only way to go? Thanks! ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
