Bei Liu (Volt) wrote:
When use "AsyncWait" it didn't give error dialog. When use "check", it
gave the error dialog.
Which error dialog?
Error 1722
Then that means MSI got back a non-zero exit code. I've never seen any
other instance of a 1722.
Can you confirm if the following is the right syntax, are 1) and 2)
the two custom actions you mention before?
1) <CustomAction Id='InstallA' BinaryKey='A' Return='asyncWait'
Execute='rollback'
ExeCommand=' B' />
..................................
<InstallExecuteSequence>
2) <Custom Action='InstallA'
Sequence='6501'>
NOT Installed
</Custom>
</InstallExecuteSequence>
You're not defining two custom actions. The one that performs the action
needs to be a deferred CA. The second rolls back the results of the
other and needs to be scheduled just before it and be marked as a
rollback CA.
--
sig://boB
http://bobs.org
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
