Install Time™ Walk Throughs - Actions

Set a Property Value

1) drag the Set Property Value action to the location in the sequence where you want the action to occur.
2) Select or type in the property you want to set in the Property field
3) fill in the Properfy Value field with the formatted value to set the property to.
4) Select any other desired Behavior attributes.

Set a Directory value

1) drag the Set Directory Value action to the location in the sequence where you want the action to occur.
2) Select or type in the directory you want to set in the Directory field
3) Fill in the Formatted value field with the formatted value to set the directory to.
4) Select any other desired Behavior attributes.

Display a Fatal Error Message

1) Drage the Display Fatal Error Messae action to the location in the sequence where you want the action to occur.
2) Type in the formatted message you want to display in the Error message field.
3) Condition the action properly in order for it to exit the install in failure conditions.

To Run an .ExE that is stored in the binary table

1) drag the Execute EXE action to the location in the Sequence where you want the action to occur.
2) Ensure that .Exe Source is set to Binary Table
3) Select an existing binary table key or select 'new' under the Binary File property. Select the .Exe for the custom action.
4) Select any other desired Behavior and Scheduling attributes.

To Run an .Exe contained in the Install

1) drag the Execute EXE action to the location in the Sequence where you want the action to occur.
2) Change .Exe Source to "Installed File"
3) Select the file from the Installed File field to run.
4) Set any command line parameters in the Command Line Field
5) Select any other desired Behavior and Scheduling attributes.
6) Be careful to properly condition this action so that is does not occur during uninstall after the file has been removed.

To Run an .Exe on the destination machine

1) drag the Execute EXE action to the location in the Sequence where you want the action to occur.
2) Change .Exe Source to "File on Destination"
3) Use formatted text to specify the file to run, including command line parameters, in the Formatted Command Line field. This should begin with a bracketed property so that it runs on any system. For, example, the following will run notepad on any system: [SystemFolder]notepad.exe It is also good to enclose the .EXE name in quotes to ensure any spaces are accounted for in the .exe path.
4) Be sure to set the working directory to a property to ensure the custom action runs.
5) Select any other desired Behavior and Scheduling attributes.

To Run an .Exe that is specified by a Property value

1) drag the Execute EXE action to the location in the Sequence where you want the action to occur.
2) Change .Exe Source to "Property Value"
3) Type or Select a property in the Property (.Exe) field that will contain the path to the .EXE to run.
4) Set any command line parameters in the Command Line Field
5) Select any other desired Behavior and Scheduling attributes.

To Run a short VBScript or JScript stored in the custom action table

1) drag Execute JScript or Execute VBScript action to the location in the sequence where you want the action to occur.
2) Change the Script Source Property to Custom Action Table
3) Enter the script in the Short script code property, using the large text editor if necessary
4) Select any other desired Behavior and Scheduling attributes.

To Run a VBScript or JScript stored in a Property Value

1) drag Execute JScript or Execute VBScript action to the location in the sequence where you want the action to occur.
2) Change the Script Source Property to Property Value
3) Type or Select the property name in the Property field
4) Optionally, type the script in the Property Script field. If the property value is set at run time, this step is not necessary.
5) If the script contains a function that should be called, you can enter the Function name in the Function name field. This must be a function and not a VBScript Sub.
6) Select any other desired Behavior and Scheduling attributes.

To Run a VBScript or JScript stored in a the Binary table - for larger scripts

1) drag Execute JScript or Execute VBScript action to the location in the sequence where you want the action to occur.
2) Change the Script Source Property to Binary Table
3) Select an existing binary table key or select 'new' under the Binary File property. Select the .Exe for the custom action.
4) If the script contains a function that should be called, you can enter the Function name in the Function name field. This must be a function and not a VBScript Sub.
5) Select any other desired Behavior and Scheduling attributes.

To Run a VBScript or JScript installed onto the destination computer

1) drag Execute JScript or Execute VBScript action to the location in the sequence where you want the action to occur.
2) Change the Script Source Property to "Installed File"
3) Select the file from the Installed File field to run.
4) If the script contains a function that should be called, you can enter the Function name in the Function name field. This must be a function and not a VBScript Sub.
5) Select any other desired Behavior and Scheduling attributes.

To call a Windows Installer .DLL that is stored in the binary table

1) drag the Call Installer DLL method action to the location in the Sequence where you want the action to occur.
2) Ensure that .Dll Source is set to Binary Table
3) Select an existing binary table key or select 'new' under the Binary File property to add a new entry. Select the .Dll for the custom action.
4) Select the name of the function to call in the Function name field
5) Select any other desired Behavior and Scheduling attributes.

To call a Windows Installer .DLL contained in the Install

1) drag the Call Installer DLL method action to the location in the Sequence where you want the action to occur.
2) Change .Dll Source to "Installed File"
3) Select the file from the Installed File field to run.
4) Select the name of the function to call in the Function name field
5) Select any other desired Behavior and Scheduling attributes.
6) Be careful to properly condition this action so that is does not occur during uninstall after the file has been removed.

To call a non-Windows installer (custom) .DLL that is stored in the binary table

1) drag the Call Custom DLL method action to the location in the Sequence where you want the action to occur.
2) Ensure that .Dll Source is set to Binary Table
3) Select an existing binary table key or select 'new' under the Binary File property to add a new entry. Select the .Dll for the custom action.
4) Select the name of the function to call in the Function name field
5) Select the Parameters to use in the call. See the parameters section below on details for setting up parameters
6) Optionally, select the return type and property to store the return value in.
7) Select any other desired Behavior and Scheduling attributes.

To call a non-Windows Installer (custom) .DLL contained in the Install

1) drag the Call Custom DLL method action to the location in the Sequence where you want the action to occur.
2) Change .Dll Source to "Installed File"
3) Select the file from the Installed File field to run.
4) Select the name of the function to call in the Function name field
5) Select the Parameters to use in the call. See the parameters section below on details for setting up parameters
6) Optionally, select the return type and property to store the return value in.
7) Select any other desired Behavior and Scheduling attributes.

To call a non-Windows Installer (custom) .DLL based on a formatted string on the destination computer

1) drag the Call Custom DLL method action to the location in the Sequence where you want the action to occur.
2) Change .Dll Source to "Formatted Path"
3) Enter a path based on a property value to the destination .DLL. For example, [System64Folder]user32.dll will point to the user32.dll in the 32 bit system folder on 64 bit Windows systems.
4) Select the name of the function to call in the Function name field
5) Select the Parameters to use in the call. See the parameters section below on details for setting up parameters
6) Optionally, select the return type and property to store the return value in.
7) Select any other desired Behavior and Scheduling attributes.

Custom Call Parameters

Specify the exact order and type of parameters required for the .DLL function call. Certain data types such as NULL, InstallHandle, and DatabaseHandle do now allow values or data formats to be specified. Structure parameters can be set up by selected the Structure data type and adding the parameters to the structure itself by clicking on the value field for the structure.


Example custom call:
call MessageBoxW in user32.dll


parameters:
NULL (parent window handle)
UnicodeString Property INSTALLDIR (message box content)
UnicodeString Normal Message Caption (message box title)
DWORD Normal 1 (message box style - 1 is OK button





All trademarks and copyrights on this page are owned by their respective owners.