In article <[EMAIL PROTECTED]>,
Kelly Leahy <[EMAIL PROTECTED]> writes:
> The problem is the sequencing. By the time InstallFinalize has happened,
> the install is already committed, so you can't roll back the install of
> version 2, at least if I'm understanding it correctly. You probably want
> your RemoveExistingProducts to be somewhere earlier in the sequence, so
> that it can cause a rollback of version 2's install if version 1's
> uninstall fails.
I always recommend putting RemoveExistingProducts right after
InstallInitialize. This wraps the entire upgrade in a transaction.
If the transaction fails, then the new version is removed and the old
version is restored. This requires that you author appropriate
rollback support in your custom actions, but you should be doing that
anyway.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
