Custom Actions added automatically by Wise products

Article:HOWTO4463  |  Created: 2006-08-02  |  Updated: 2007-04-11  |  Article URL
Article Type
How To


What are the custom actions added automatically by Wise's Windows Installer Editor or Wise for Windows Installer?


When authoring installation databases, you are aware of the standard actions that take place during a Windows Installer installation. You might also be aware that in addition to these standard actions, you can create custom actions to do things like call executables or .DLL files. Did you know that Wise products contain built-in custom actions that are automatically added to your installation?

This article provides an overview of what those custom actions are and under which circumstances Wise products will add them to your installation. There are many built-in custom actions in Wise for Visual Studio .NET, Wise Package Studio, and Wise for Windows Installer added by default to enhance or add functionality to Microsoft Windows Installer*. When you create custom actions that call a .DLL or use certain features, such as the Upgrades page within Wise products, the built-in custom actions listed below are added to your installation automatically.

Note: Removing these Wise custom actions might cause problems with your installation.

  • SetPatchMode—This custom action is added by default to every installation before you begin customization. It is added whether your installation uses patching or not, but it has no effect on installations that do not use patching. It adds functionality to the Windows Installer patching process by setting the REINSTALL property to the list of features in the previous version of the software. This action also sets the ADDLOCAL property to the list of features, if any, added to the installation in the new version of the software. This action is sequenced after the LaunchConditions standard action.
  • SetPatchReinstallMode—This action sets the REINSTALLMODE property to "omus" (the Windows Installer default) so patches can work around issues with the Windows Installer patching process. This action is sequenced after the SetPatchMode custom action. After you add a custom action to your installation that calls a .DLL with parameters or calls a WiseScript, the actions listed below enhance Windows Installer's functionality.
  • WiseStartup—This action adds additional code to enable better parameter passing for actions that call a .DLL file. This action is sequenced after the normal User Interface sequence is executed.
  • WiseCleanup—This action adds additional code to clean up any temporary files left over from custom actions. This action is sequenced after the ExecuteAction standard action.
  • WiseAltStartup—This action saves the current state of properties for use by the custom actions. This action is sequenced after the MigrateFeatureStates standard action.

When you add upgrade information to the Upgrades page in Installation Expert, the actions listed below are automatically added  to your installation.

  • WiseUpgradeCheck—This action works around issues where the Windows Installer runtime does not detect previous versions of the application.
  • WiseUpgradeCheckEx—This action, added with WiseUpgradeCheck, works around issues where the Windows Installer runtime does not detect previous versions of the application.

The custom action listed below adds functionality for creating single file .EXE setup programs.

  • WiseSingleFileCheck—Removes cached copies of the .MSI file that are extracted during uninstalls.

You have the ability to call your own custom actions when customizing a Windows Installer database. This article has described built-in custom actions that Wise products automatically add to your installation based on certain criteria. Knowledge of these built-in custom actions helps you understand the changes occurring in your installation when you create upgrades or use custom actions that call .DLL files. With this knowledge, you can design more robust installations and more easily troubleshoot runtime errors.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices