It seems to me like the roll of burn and msiexec as it is related to the MajorUpgrade element is confused in this and related threads. AFAIK candle compiles the MajorUpgrade element and the MajorUpgrade/@Schedule into the msi package which is parsed by msiexec at installed time without any involvement of Burn.
I use a Burn bootstrapper to drive a chain of msi packages. There is a concept of a Burn 'major upgrade' but it is unrelated to the MajorUpgrade element. I have a number of Burn driven products. I make sure that bootstrapper's Product/@Version changed for each build (even when nothing else is changed, and also use Product/@="*" ) and I have not had any problems with the upgrade behavior. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Force-a-MajorUpgrade-to-do-complete-uninstall-BEFORE-new-install-tp7597686p7597712.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
