execute deferred and properties

  • Thread starter Thread starter Glenn M
  • Start date Start date
G

Glenn M

MSI documentation says thay for every custom action you shoudl have a
rollback action . and you can only have a rollback action if you place
the custom action in execute defferred.

however if your custom action runs based on a condition (e.g
remove="all") that condition can only be evaluated during the execute
immediate stage.

how do you evaluate the condition at execute deferred time. do you
store it in a property at execute immediate time and they grab that
property during the execute deferred sequence?

thanks

glenn
 
That only applies to custom actions that modify the target machine. These
should be deferred, and accompanied by a rollback action.
You can use properties in the condition because the condition is evaluated
when the execute script is generated.
See the following article for additional explanation:

Installation Phases and In-Script Execution Options for Custom Actions in
Windows Installer
http://www.installsite.org/pages/en/isnews/200108/index.htm

--
Stefan Krueger
Microsoft Windows Installer MVP

Please post your questions in the newsgroup or vist one of these web sites:

Windows Installer FAQ
http://www.msifaq.com - http://www.msifaq.de

InstallSite - Resources for Setup Developers
http://www.installsite.org
http://www.installsite.de (GERMAN)
 
Back
Top