Rob Mensching-7 wrote > > Or use MajorUpgrade element. <smile/> >
I don't think that the MajorUpgrade element gives me the flexibility that I need. My assumptions (and what I believe to be best practice) are: 1. The UpgradeCode is fixed for all versions of the product. 2. The Product Id is set to "*" so a new GUID will be generated for each build of the installer. Here is the situation: 1. We allow multiple versions of our product to be installed at the same time if they have a different Major.Minor version. I don't believe that the MajorUpgrade element supports this option. The UpgradeVersion elements shown should provide for this. 2. Within the same Major.Minor version the user can upgrade or downgrade the product. The AllowDowngrades attribute of the MajorUpgrade element does support this. I realize that there could be other approaches to implementing this such as using a new UpgradeCode for each Major.Minor version. I thought that my current approach would be closer to what Windows Installer intended. Comments? -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bug-UpgradeVersion-element-causing-LGHT0094-error-tp7579387p7579403.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
