Yeah, I was always leaning that way as well. However, I didn't think really
hard if there was ever a case you'd want them separated. Anyone have scenarios
where you'd need a RestartBoundary without a RollbackBoundary?
_______________________________________________________________
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, December 9, 2014 8:43 AM
To: WiX toolset developer mailing list
Subject: Re: [WiX-devs] Old topic: Burn reboot checkpoint / reboot boundary
I have always thought this should be an extension to the RollbackBoundary
element, e.g. RebootIfRequire="yes" as it seems logical that a reboot boundary
would be a rollback boundary.
Neil
From: Tobias Erichsen [mailto:i...@tobias-erichsen.de]
Sent: 09 December 2014 16:26
To: wix-devs@lists.sourceforge.net<mailto:wix-devs@lists.sourceforge.net>
Subject: [WiX-devs] Old topic: Burn reboot checkpoint / reboot boundary
Hi everyone,
I was thinking about looking into an old topic where one
could specify a RebootBoundary somewhere in the chain
and make sure that all prior MSIs requests for reboot
will be executed at that point:
http://wixtoolset.org/issues/4026
Anyone got any ideas, thoughts etc. about this topic before
I dive into this?
Best regards,
Tobias
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
