I think there is a misunderstanding of the linked article. Treat each Bundle and each MSI as if you are following the rules for a Major Upgrade. While the Bundle is processed by Burn and not msiexec, it should have an UpgradeCode which does not change for each build of the Bundle. Make sure that each build of the Bundle/@Version increments (in any of the four parts), if anything (Bundle or packages) are changed. The equivalent concept of a 'ProductCode', the Bundle Id is changed under the covers for each build.
Each MSI should follow the Major Upgrade rules to do what you indicated. The UpgradeCode for each MSI is typically unique to that MSI package and unrelated to the UpgradeCode of the Bundle, at least in my experience. (I'm sure that there might be some special situations where different packages share an upgrade code, but to achieve what you outlined that is not necessary.) -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Updating-Replacing-existing-MSI-with-Burn-bundle-tp7598911p7598914.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
