I'm bumping this thread since I really need help with this problem. In a nutshell, the question is this:
*During an upgrade, what can cause that one of the /unchanged/ msi's won't get the new bundle id registered as a dependency in the registry, which makes Burn wanting to uninstall it?* This is pretty much the gist. Hopefully one of the Burn developers can give me some insight.... //Caisa -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Really-weird-upgrade-problem-tp7580416p7580466.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
