Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION EXPRESS V1.0 Installation Manual page 93

Windows Installer Editor Reference
Product Code
Every Windows Installer installation must have a unique product code, which is used
as the principal identification for the application. Windows Installer Editor generates
a product code in the form of a GUID, which ensures that no two applications ever
have the same product code. To change the product code:
Select its value and click the Change button.
On the dialog box that appears, click Yes to change the product code and the
upgrade code, or click No to change just the product code. If the installation is
an upgrade of an existing installation, then change the product code only.
See Upgrades on page 292.
Changing the product code also changes the package code. For information on
the product and package codes, see ProductCode Property, Package Codes, and
Product Codes in the Windows Installer SDK Help.
See About GUIDs on page 488.
Application Type
Specify whether this is a standard Win32 or a .NET installation. This also determines
how Windows Installer Editor handles COM interoperability registry entries. This
defaults to the Default Application Type that is specified in Wise Options.
See Setting .NET Assembly Options
The ability to create .NET installations is supported only by Windows Installer 2.0 or
later.
Win 32 (non .NET)
Select this if this is a standard Win32 installation without .NET assemblies.
.NET Application
Select this if this is a .NET installation with only .NET elements.
Mixed (.NET and Win32)
Select this if this installation contains both Win32 and .NET elements. When this
option is selected, the Generate COM interop registry keys for .NET
Assembly check box on the File Details dialog box > Self-registration tab is
marked by default for all .NET assemblies you add to this installation. The
assemblies will be registered so that they can be called as though they were
COM elements.
When the .NET Application or Mixed option is selected, entries are created in the
MsiAssembly and MsiAssemblyName tables for each assembly you add to the
installation. The Global Assembly Cache directory also appears on the Files page.
Installation Target
This value is for meta data purposes only. It does not change the installation.
Description
Describe the package.
Don't update or recompress files when saving
(.MSI files only.) Files are stored in .MSI files either with a hard-coded path to the
original, or without a path. For files with paths, Windows Installer Editor gets the
latest copy of the file from the specified path when you save or compile the .MSI.
Mark this to prevent Windows Installer Editor getting the latest copy of files that
have paths.
Defining an Installation Project
on page 36.
93