Chapter 1: Introduction; About Wisescript; Wisescript Benefits - Symantec WISESCRIPT EDITOR 7.0 SP2 - FOR WISE INSTALLATION EXPRESS V1.0 Installation Manual

Chapter 1
Introduction

About WiseScript

WiseScript Benefits

WiseScript Editor Reference
This chapter includes the following topics:
About WiseScript on page 12
WiseScript Benefits on page 12
Starting the Software
The Product Interface
Using WiseScripts in a Windows Installer Installation
Compiling, Testing, and Running a WiseScript
Product Documentation
WiseScript Editor is a WiseScript™ authoring environment that you can use to automate
administrative tasks. You also can use it to create .EXEs to use as custom actions in
Windows Installer installations. These custom actions can extend the capabilities of
Microsoft Windows Installer and simplify installation tasks (example: parsing and
arithmetic functions) that are difficult to accomplish with Windows Installer.
WiseScript Editor is embedded within Windows Installer Editor and appears when you
create a custom action that calls a WiseScript.
WiseScript is a high-level scripting language that consolidates dozens or hundreds of
lines of code into predefined script actions.
What Makes WiseScript Unique
Easy to learn
WiseScript supports a point-and-click method of scripting. The script author is
prompted for the parameters needed by each script action, so a script can be
created and tested very quickly. The script is displayed in clear, English-like
statements. For those who need additional flexibility and control, WiseScript
provides advanced features (examples: IF blocks, WHILE loops, UI dialog boxes).
No runtime needed
WiseScripts are compiled into self-contained .EXEs that do not require an agent or
runtime files on the destination computer.
Compact size
A WiseScript .EXE is small in size (about 100 KB). If a script uses any files that may
not be on the destination computer, it can compress those files into the .EXE.
(Example: A script that detects and removes spyware might temporarily install
Kill.exe on the destination computer while the script is running.)
on page 13
on page 14
on page 15
on page 16
on page 14
12