Setting General Options - Symantec WINDOWS INSTALLER EDITOR 8.0 Reference

Hide thumbs Also See for WINDOWS INSTALLER EDITOR 8.0:
Table of Contents

Advertisement

Setting General Options

Windows Installer Editor Reference
Setting Source Control Options
Setting Wildcard Groups
To set general options, select Tools menu > Options and click the General tab.
Automatic Options
Create backup copy during save
Mark this to create a new backup file every time you save. The backup file name
consists of the current file name plus a number. (Example: if the current file name is
Sample.wsi, the backups are named Sample1.wsi, Sample2.wsi, and so on.) Only
the file you are working on is backed up. (Example: if you open a .WSI and save it,
the corresponding .MSI is not backed up.) Use caution with this option if you are
working with large installation files; if you save often, your disk space will quickly
become depleted.
This can be set automatically from Wise Package Studio Preferences; use this check
box to override the Package Studio setting.
Add default remarks to installation sequences
Although most Wise project (.WSI) files have remarks that explain the actions in the
sequences, compiled .MSIs do not. Mark this to add remarks to the current .MSI and
all .MSIs that you open subsequently. Remarks are added to .WSIs only if no
remarks already exist.
Create XML copy during save
Mark this to update a copy of the installation in XML format every time you save. If
a copy does not exist, it is created. The copy has the same name as the installation
file with the extension .XML appended, and it is saved in the same directory.
(Example: If the current file name is Application.wsi, the XML copy is named
Application.wsi.xml.) This lets you check the XML version of the installation into a
source code control system and use text-based file comparison tools to find
changes.
See
Saving an Installation as XML
Compiler Options
The following options are default settings for all new compiles. Changing these settings
does not affect installations that have already been compiled.
Add custom actions for predefined folders in merge modules
This affects the merging of merge modules that place files in predefined directories,
such as \Windows, \System32, and so on. Mark this to have the merge emulate the
behavior of the Microsoft merge tool, mergemod.dll, which uses custom actions to
handle predefined directories. Clearing this check box can fix potential problems
with capitalization inconsistencies in the directory name.
on page 46
on page 47
on page 77.
Setting Up
34

Advertisement

Table of Contents
loading

Table of Contents