Windows Installer
 
Unrestricted access to Windows Installer functionality!
 
Open Source
 
Open source!
 

<xml/>

 
Plain XML based source scripts!
 
Free
 
Free, no strings attached!
 
Build Automation
 
Command-line interface for automated application build process!
 
Community
 
Thriving community support!
Why WiX?
How can I provide data to my deferred custom action?

Deferred custom actions have limited access to the installation session. If your deferred custom action requires information about the installation that it cannot obtain through its limited access, then you can provide that information to the deferred custom action through the CustomActionData property. This method is only available to script and DLL deferred custom actions. This is how it works:

1. An immediate custom action that executes before the deferred custom action sets a property with the same name as the deferred custom action to the value that is needed by the deferred custom action. So, if the primary key for a deferred custom action is called "DeferredCA," then the immediate custom action would set a property called "DeferredCA" to the value that was needed. A type 51 custom action would be an easy way to set this property. Another method would be an immediate custom action that calls MsiSetProperty with the szName parameter equal to "DeferredCA." Note: The action name is case-sensitive.
 
2. When the deferred custom action is queued into the installation script, the installer will write the value of the property "DeferredCA" into the installation script as the value of the property CustomActionData.
 
3. Upon execution, the deferred custom action retrieves the value by making a MsiGetProperty call with the szName parameter equal to "CustomActionData." Alternatively, a script custom action would use the Property property of the Session object.