Table of Contents
Advertisement
Troubleshooting Custom Actions
Windows Installer Editor Reference
6.
On the Events tab, in the Publish Events group box, click Add and complete the
dialog box:
Event
Select DoAction.
Argument
Enter the name of the custom action. The name is case-sensitive.
When the installation is run, the button you added appears on a dialog box. When the
end user clicks the button, the custom action you specified is run.
If a custom action doesn't work:
Try moving it to a different sequence, or to a lower position in the current sequence.
Does the custom action require elevated privileges? If so, try running it in the
Execute Deferred sequence. On the custom action's Properties tab, set the In-
Script Options drop-down to Deferred Execution - System Context.
Make sure the custom action name is unique. To quickly survey your custom
actions, select All Custom Actions from Installation Mode.
Does the custom action reference a Windows Installer property, such as REMOVE?
Windows Installer standard actions set Windows Installer properties. It could be that
the property your custom action is referring to is not set yet. Use the debugger to
discover whether the property is set at the point where you expect it to be set. Keep
moving the custom action down in the sequence until it works.
Is the installation trying to change restricted public properties? The ability to do this
depends on several factors.
See Restricted Public Properties in the Windows Installer SDK Help.
Using MSI Script
450
Advertisement
Table of Contents
Troubleshooting
