Microsoft® Visual Studio® 2010 Unleashed

The Custom Actions Editor

If you have unique installation requirements not covered by the provided set of setup activities, you can implement them using the Custom Actions Editor. For instance, your software might need to register itself over the Internet. The Custom Actions Editor isn’t used to actually build the custom action per se; it merely lets you identify an executable or script file that needs to be run and when that file should be run during the install process. There are four phases from which we can pick: Install, Commit, Rollback, and Uninstall. In our example, if we want to run a .exe file to register the CSR application over the Internet, we might want to make that happen in the Install phase, with a corresponding action in the ...