Cool -- I merged Sean's pull request.
On 16-Jul-14 16:48, Hoover, Jacob wrote:
Last message got held up due to size, so resending.
I've finally figured out what I think the workflow is doing and I
now think Sean is right. Just my one liner change needs to be removed.
The A bundle is downloading bundle B, placing it in the per-user
cache, invoking the exe, and then removes it. Since the exe is
running, the engine then handles this via a MoveFileEx call which
moves the exe to the %TEMP% folder, and schedules it for deletion.
This ensures that is the user cancels the upgrade the file is
removed. If the user applies the upgrade, then the application of
said upgrade would re-cache the package as needed in the appropriate
location.
Thanks,
Jacob
--
sig://boB
http://joyofsetup.com/
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
WiX-devs mailing list
WiX-devs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-devs
