Re: [WiX-users] Burn: Really weird upgrade problem.

2012-09-13 Thread Miss Parker
/[170C:1710][2012-09-10T13:43:58]: Detected related package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version: 2.1.0.0, language: 0 operation: MajorUpgrade [170C:1710][2012-09-10T13:43:58]: Detected related package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version:

Re: [WiX-users] Burn: Really weird upgrade problem.

2012-09-13 Thread Rob Mensching
There are a number of mysterious things in this log that need more information to debug. For example: [170C:1710][2012-09-10T13:43:58]: Detected related package:{02BA91DA-3C08-45ED-854E-343B5BBDCE40}, scope: PerMachine, version: 2.1.0.0, language: 0 operation: MajorUpgrade [170C:1710][2012-09-10T1

Re: [WiX-users] Burn: Really weird upgrade problem.

2012-09-13 Thread Miss Parker
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

Re: [WiX-users] Burn: Really weird upgrade problem.

2012-09-12 Thread Miss Parker
Ok, thanks. I'll keep an eye on your thread. //Caisa -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-Really-weird-upgrade-problem-tp7580416p7580441.html Sent from the wix-users mailing list archive at Nabble.com. ---

Re: [WiX-users] Burn: Really weird upgrade problem.

2012-09-12 Thread Tim Comport
This sounds very similar (the same) to the problem I have been struggling with for a while. http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-Upgrade-Issue-tt7579392.html Just did some more testing today, about to update above thread with my findings. -- View this messag