Custom Actions Management in Deployment
The Custom Actions Editor allows you to specify additional actions to be performed on the target computer at the end of an installation. For example, you might want to run a program that associates a server component with a particular message queue.
Custom actions must be compiled as a .dll or .exe file, or added to a project as a script or assembly before they can be added to a deployment project. Actions can only be run at the end of an installation.
The editor contains four folders, each corresponding with a phase of installation: Install, Commit, Rollback, and Uninstall.
Custom actions are run in the same order that they are displayed in the editor. Custom actions can be reordered by dragging with the mouse or by using the Cut and Paste commands on the Edit menu.
In This Section
- How to: Add and Remove Custom Actions in the Custom Actions Editor
-
Describes how to specify custom actions to be run during installation, and how to specify the order of execution for custom actions.
- How to: Add Predefined Custom Actions in the Custom Actions Editor
-
Explains how to add custom actions that are included in Visual Studio.
- Error Handling in Custom Actions
-
Describes how to add error-handling code to a custom action.