User Guide
514
Call JScript From Property
This custom action runs JScript code that is stored inside a Windows Installer property.
You might store the script in a property if part or all of the script needs to be generated
dynamically based on end user input or system configuration.
Tips
! The script is limited to 32 Kb, which is the size limit for Windows Installer properties.
! Use the script to read and write properties to the installation.
! The destination computer must contain the script’s runtime.
Usage
Double-click the custom action and complete the Details tab:
! Custom Action Name
Enter a unique name that begins with a letter or underscore. It can contain numbers
and periods. It must not match the name of any Windows Installer standard action.
See Standard Actions Reference in the Windows Installer SDK Help.
! Property
Specify a property that stores the script, either by selecting a property or typing a
new property name. Elsewhere in the installation, you must provide a mechanism for
populating this property with the script text.
! Script Function Call
(Optional.) Type the name of the function within the script to call.
! Run Script in Win64 Process
Mark this if the script file is 64-bit. If the script file is 32-bit, leave this cleared.
(Available only in 64-bit installations.)
Also see:
Guidelines for Calling VBScripts and JScripts on page 502
Guidelines for Custom Action Location on page 499
Using the Custom Action Properties Tab on page 534
Using the Custom Action Location Tab on page 532
Custom Action Type 53 in the Windows Installer SDK Help
Call VBScript From Embedded Code
This custom action runs VBScript code that is embedded inside this custom action.
Tips
! The script is limited to 255 characters; use other VBScript custom actions for longer
scripts.
! The destination computer must contain the VBScript runtime.
Usage
Double-click the custom action and complete the Details tab:
! Custom Action Name
Enter a unique name that begins with a letter or underscore. It can contain numbers
and periods. It must not match the name of any Windows Installer standard action.
See Standard Actions Reference in the Windows Installer SDK Help.