I don't know enough about Burn, so I don't know if it can do this but... I think that what you want is both MSIs installed as single MSI transaction, wrapped in MsiBeginTransaction/...EndTransaction etc. Then if b.msi fails the entire (a + b) transaction rolls back, including the major upgrade of your a.msi, back to the previous product version of a, assuming your major upgrade RemoveExistingProduct placements are within each individual MSI transaction area InstallInitialize=>InstallFinalize. There are some gotchas to doing this (things you can't do within the MSI) so even if Burn supports this your MSI packages may not be compatible with a single transaction.
http://msdn.microsoft.com/en-us/library/windows/desktop/bb736322(v=vs.85).as px Phil -----Original Message----- From: Simon Fogliato [mailto:sfogli...@deltacontrols.com] Sent: Wednesday, June 26, 2013 11:22 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Bootstrapper multiple MSI's don't rollback to a working installed state In the context of the bootstrapper chain rollback event the individual MSI MajorUpgrade Schedule element is irrelevant since this only comes into play when rolling back 1 MSI. In my case a.msi has been upgraded successfully therefore the old existing product is removed. Then when b.msi fails a.msi is simply uninstalled. If only there was a MajorUpgrade Schedule element for a bootstrapper bundle, then I would have something to tinker with. However I would like to note that I have tried all 5 scheduled cases inside a.msi and b.msi just to confirm my findings... <MajorUpgrade DowngradeErrorMessage="A newer version is already installed." Schedule="afterInstallValidate" /> <MajorUpgrade DowngradeErrorMessage="A newer version is already installed." Schedule="afterInstallInitialize" /> <MajorUpgrade DowngradeErrorMessage="A newer version is already installed." Schedule="afterInstallExecute" /> <MajorUpgrade DowngradeErrorMessage="A newer version is already installed." Schedule="afterInstallExecuteAgain" /> <MajorUpgrade DowngradeErrorMessage="A newer version is already installed." Schedule="afterInstallFinalize" /> -----Original Message----- From: Nick Ramirez [mailto:nickra...@hotmail.com] Sent: Wednesday, June 26, 2013 9:36 AM To: wix-users@lists.sourceforge.net Subject: Re: [WiX-users] Bootstrapper multiple MSI's don't rollback to a working installed state How is the MajorUpgrade element scheduled in your MSI? By default it is "afterInstallValidate", which does not bring back the old version if there is a rollback. See the documentation at http://wix.sourceforge.net/manual-wix3/wix_xsd_majorupgrade.htm. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Bootstrapper-m ultiple-MSI-s-don-t-rollback-to-a-working-installed-state-tp7586867p7586868. html Sent from the wix-users mailing list archive at Nabble.com. ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ---------------------------------------------------------------------------- -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
