Actually ... Once again I can confirm exactly the same behavior with my bundle and one of the included MSI packages. I just didn't realize what I was seeing until I saw your description. I also have a systray app that fails to "restart" and I occasionally get a spontaneous reboot when installing from an update bundle. Now that I look closely at the logs, I have one component that inverts the install order as Neil describes, with no difference at all in any aspect of the bundle definition. In fact, the bundle definition is generated from another XML artifact and and XSLt stylesheet, so it *can't* be any different.
It hasn't been that big a deal because once the bundle is installed, the MSI applications support a self update process that updates components of the bundle with dependency management from a central service. People rarely (if ever) update from a new bundle. Cheers. On 12-12-12 03:06 PM, Neil Sleightholm wrote: > Still really struggling to understand this and the more I look the more I > think something odd is happening burn. > > This is the problem: > When I run an install created with burn that upgrades an existing install I > see that burn runs the new MSI install and then the old MSI uninstall. This > only happens for one of four MSIs in the package which were all authored by > me in the same way. If I run the MSI outside of burn it does the upgrade and > everything looks ok, there is only one entry in ARP programs and the > HKCR\Installer registry looks ok. > > Even running it with burn what is left on the machine after the upgrade is > correct and the only reason I notice it is that as part of my uninstall > process I stop a tray application running; so with this problem the tray > application is not running after the install. > > I can probably live with this but would really like to understand why burn > thinks my application has not upgraded and needs to run the uninstall. In > some cases the uninstall phase detects a reboot is required but burn doesn't > reflect this in the UI and when you click close the machine reboots without > warning. > > So my question is how does burn detect that an MSI hasn't upgraded and it is > necessary to launch another instance to do the uninstall? > > Any other insights in to this problem would be greatly appreciated. I would > also ask you check your logs and see if you are getting the same problem; the > key is that there are two log files from the main burn package. > > Regards > > Neil > > ------------------------------------------------------------------------------ > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial > Remotely access PCs and mobile devices and provide instant support > Improve your efficiency, and focus on delivering more value-add services > Discover what IT Professionals Know. Rescue delivers > http://p.sf.net/sfu/logmein_12329d2d > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users -- Steve Hole (780)438-1981 (hm) (780)905-9116 (mb) ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
