Windows Installer Editor Reference
68
Working With Wise Installation Files
z
The application’s system requirements in as much detail as possible. Consider not
only memory and disk requirements, but also the minimum screen depth and
resolution, and the minimum required version of the operating system.
z
Any custom graphics, referred to as billboards, that should be displayed during
installation.
z
Any changes that should be made to the dialog boxes that will be displayed during
installation.
See
Using the Dialogs Page
on page 452.
z
If applicable, a Readme file and a license agreement file.
File Types
In Windows Installer Editor, you can create and edit different types of Windows Installer
database files. You can work in the Windows Installer database file or in a project file
that contains instructions for compiling the Windows Installer database file.
See
Project Files and Database Files
on page 69.
Following are the types of Windows installer files.
Extension
Description
.MSI
Windows Installer database, which is a distributable installation. The .MSI extension is
associated with the Windows Installer executable, MSIExec.EXE. When an .MSI is
opened, Windows Installer executes it, thereby installing the application. You can open
and edit an .MSI in Windows Installer Editor. However, options that have to do with
creating an .MSI, such as those on the Releases, Release Settings, and Media pages,
are unavailable.
You can convert an .MSI to a project file (.WSI).
See
MSI to WSI Conversion
on page 399.
.WSI
Windows Installer project file, which describes an .MSI but does not store contents. It
is in the same format as an .MSI. You edit a .WSI in Windows Installer Editor and
compile it to the corresponding .MSI. The .WSI file is smaller than an .MSI and you can
set multiple options for the output of the .MSI.
.WSPROJ
(Visual Studio integrated editor only) Visual Studio project file for a Windows Installer
installation. When you create an installation project in Visual Studio, a corresponding
.WSPROJ file is created in the same location. The .WSPROJ file points to the .WSI.
.MSM
Windows Installer merge module, which is a pre-compiled library of components (files,
registry changes, and other system changes) that installs a discrete part of your
application. It cannot be run alone, but must be merged with an .MSI during the .MSI
compile.
See
About Merge Modules
on page 364.
.WSM
Windows Installer merge module project, which describes an .MSM, but does not store
merge module contents. You edit a .WSM in Windows Installer Editor and compile it to
the corresponding .MSM.
See
About Merge Modules
on page 364.
.MST
Windows Installer transform, which changes a Windows Installer package at run time
and must be applied from the command line. See
About Transforms
on page 384.