Get Temporary Filename; Get Windows Installer Property; Halt Compilation - Symantec WISESCRIPT EDITOR 7.0 SP2 - FOR NS V1.0 Manual

Get Temporary Filename

Get Windows Installer Property

Halt Compilation

WiseScript Editor Reference
This action generates a unique, temporary file name and stores it in a variable. Use the
temporary name when you need to install a file to the Windows Temp directory
(%TEMP%). Files that you create using this file name are deleted when the installation
finishes. Example: Use this to install a .DLL that is called during installation, and is then
no longer needed.
To complete the dialog box
Variable
Specify a variable in which to store the temporary file name. Only a file name is
generated. To refer to this file, prefix it with the %TEMP% variable extension.
Example: If the variable is %HELPFILE%, the full path of the file would be
%TEMP%\%HELPFILE%.
This action gets the value of a Windows Installer property in the currently running
Windows Installer installation and puts it into a WiseScript variable. Use this action only
in WiseScripts that are called from a Windows Installer installation.
Note
This action works only if you have Windows Installer Editor installed.
To complete the dialog box
Dest. Variable
Select or enter a variable to store the value of a Windows Installer property.
Property Name
Enter the name of the Windows Installer property in the currently running Windows
Installer installation.
See also:
Set Windows Installer Property
Evaluate Windows Installer Condition
This action immediately stops compilation of the script. It must be placed between
Compiler Variable If and Compiler Variable End statements or the script will never
compile. Use this to ensure that conditions are met before compiling.
To complete the dialog box
Message Text
Enter a message to display to the user if the compile is stopped.
Example: You develop a script that uses runtime files. On your own computer, you have
the correct runtime files to pull into the installation. However, you want to prevent
compilation on other computers if they lack correct runtime files because the resulting
installation could damage runtime installations on destination computers.
on page 88
on page 61
71