Summary

Synopsis

This article discusses ways to launch a custom action during the removal of a package.

Discussion

There are two ways to author the installation database such that an action is only called when the package is uninstalled:

• In the Sequences view, if the action is sequenced after the InstallValidate action in the InstallExecuteSequence table, you can specify a condition of REMOVE="ALL" for the action in the Condition column. Note that the property is not guaranteed to be set to ALL during an uninstall before the installer executes the InstallValidate action.

  Note: The quotation marks around the value ALL are required in this case.

• In the Sequences view, if the action is sequenced after the CostFinalize action and any actions that could change the feature state, such as the MigrateFeatureStates action, the action can be conditioned on the state of a particular feature or component. Use this option to call an action during the removal of a particular feature or component, which may occur outside of the complete removal of the application.

Additional Information

For more information on custom actions, refer to the following Knowledge Base articles:

Q106146 HOWTO: Executing a Custom Action Exclusively During a Patch Install

Q106229, " HOWTO: Accessing a Property with a Deferred Execution Custom Action."

Related KB Articles