User Guide

80
Options for New Installations
! Device Driver
Creates an installation that installs a device driver. This template supports Microsoft’s
Driver Install Frameworks (DIFx). It includes custom actions that install and uninstall
the device driver properly. See Creating a Device Driver Installation on page 78.
! Merge Module
See Creating a Merge Module As a New Installation on page 334. (In Visual Studio:
see Creating a Merge Module Within a Solution on page 336. If this name ends with
“File”, it creates a stand-alone file that’s not part of a solution; see Creating a Merge
Module As a New Installation on page 334.)
! Transform
See Creating a Transform Based on an Existing .MSI on page 348.
! Mobile Device Tools
(Professional and Enterprise editions only.) The following tools create an installation
for a mobile device.
• Pocket PC Application
See Creating a Pocket PC or Smartphone Installation on page 239.
• Palm Application
See Palm OS Installations on page 252.
• Smartphone Application
See Creating a Pocket PC or Smartphone Installation on page 239.
! Conversion Tools
The following tools convert an existing installation from another format to Windows
Installer format.
• SMS Installer or WiseScript Installation
See Convert SMS Installer or WiseScript Installation on page 358.
• InstallShield Professional
See Convert InstallShield Professional on page 356.
! Import Tools
The following tools open an import wizard, where you select a development project
file to import. Target file information is extracted from the project file and added to
the installation. See Import Visual Studio Projects on page 360.
• Visual Basic
(In Visual Studio: this is named Import Visual Basic.)
• Visual C#
(Not available in the Visual Studio integrated editor.)
• Visual J#
(Not available in the Visual Studio integrated editor.)
! File type options
(Wise editor only.) Select the format of the file:
• Create standard .MSI or .MSM file that contains all binary and cabinet
files
Mark this to create a new Windows Installer database file. Because the
installation file generally encapsulates all the files of the installation, an .MSI is
usually larger in size and takes longer to save. Also, some options that
determine the output of an .MSI are not available if you work with the .MSI itself.
• Create .WSI or .WSM project file that can be compiled into an .MSI or
.MSM
Mark this to create a project file instead of a installation file. Unlike .MSIs,
project files are not distributable installation files; they describe and compile a