Creating A Clean Build - Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

Table of Contents

Advertisement

Creating a Clean Build

Windows Installer Editor Reference
3.
Click Edit Script at the right of the page.
The Edit Script button is available only after you do one of the following:
Add prerequisite files or runtimes on the Prerequisites page.
Select Install the .MSI into an SVS layer on the Build Options page.
See
Setting Build Options for a Release
If you have not previously edited the script, a warning message appears. Click Yes.
The installation is saved and compiled and the WiseScript that creates the
installation's .EXE opens in WiseScript Editor.
The name of the WiseScript file for the default release is the installation name with
the extension .WSE. The WiseScript files for additional releases are named for the
release.
Warning
Don't change the name of the WiseScript file. It must have this name to create an
.EXE that includes your edits.
4.
Edit the WiseScript as needed and save it.
The next time you compile the installation, an .EXE is generated using the
WiseScript file that you edited.
5.
Thoroughly test the WiseScript to make sure it executes as expected.
To reset the WiseScript
1.
Click Reset Script at the right of the page.
This button is enabled only if you have used the Edit Script button.
A warning message appears.
2.
Click Yes.
The changes you made to the WiseScript are deleted, and the ability to add and edit
prerequisite files on the Prerequisites page is enabled.
See also:
About Script Editor in the WiseScript Editor Help
Note
This page is enabled in a .WSI only.
Use the Clean Build page if you need to perform the final build on a clean build
computer. A clean build environment helps avoid virus contamination. Also, moving a
build to a clean build computer will reveal whether some necessary files exist only on
the developer's computer.
The clean build itself is a collection of files that are necessary to compile an installation
project. This includes a minimal copy of Windows Installer Editor, an .INI file that stores
information normally stored in the registry, and all installation files. No changes are
made to the registry or system of the build computer during the build creation process.
Organizing Your Installation Into Releases
on page 216.
228

Advertisement

Table of Contents
loading

This manual is also suitable for:

Windows installer editor 7.0 sp2

Table of Contents