Call Vbscript From Embedded Code; Call Vbscript From Installation - Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

Call VBScript From Embedded Code

Call VBScript From Installation

Windows Installer Editor Reference
Guidelines for Custom Action Location
Using the Custom Action Properties Tab
Using the Custom Action Location Tab
Custom Action Type 53 in the Windows Installer SDK Help
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.
Run Script in Win64 Process
(64-bit installations only.) Mark this if the script needs to access 64-bit functionality
and run in a 64-bit process.
Enter the VBScript to execute
Type or paste the script text. Code elements, such as function names, declarations,
and values, are color-coded. You can use bracketed property names, table keys,
environment variable references, and other special substrings. See Formatted in the
Windows Installer SDK Help.
See also:
Guidelines for Calling VBScripts and JScripts
Guidelines for Custom Action Location
Using the Custom Action Properties Tab
Using the Custom Action Location Tab
Custom Action Type 38 in the Windows Installer SDK Help
This custom action stores a VBScript file in the Binary table of this installation file and
runs it during installation. During installation, the VBScript file is extracted to a
temporary directory, is run, and is deleted.
Tips
Manage the file on the Resources page, which reflects the Binary table.
Use the script to read and write properties to the installation.
The destination computer must contain the script's runtime.
on page 505
on page 542
on page 539
on page 507
on page 505
on page 542
on page 539
Custom Action Reference
521