In article <[EMAIL PROTECTED]>,
"Daryn Mitchell" <[EMAIL PROTECTED]> writes:
> Richard is right that your primary issue to that your CA has to be deferred
> if you want your rollback action to get written to the rollback script.
Right, I forgot to mention that the ICE I wrote checked that the CA
action *and* its rollback were both deferred and also:
> I wanted to add that the condition for your rollback action should be the
> same as the deferred action that you want to roll back.
it checked this too :-).
ICEs are your friend. They can find so many of these little details
that you can easily get wrong. I found that adopting a few naming
conventions for your identifiers in the MSI tables can help you write
additional checks on your data that the normal ICEs can't assume.
(i.e. they can't assume that because the action's key is MyRollbackFoo
that this is an action intended to rollback the MyFoo action.)
--
"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: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
