Windows Installer Editor Reference
393
Tools
Use as many of the application’s features as possible to ensure that files used by
rarely-used features are recorded. Do not use the application to print, because
printing accesses Windows operating system and printer-specific files.
6. Close the application, return to the Run Application dialog box, and click Finish.
If a file that is part of a merge module is added, the Files in Merge Modules dialog box
appears. It prompts you to add the merge module and, if necessary, download it.
See
Adding Merge Modules Instead of Files
on page 132.
(Requires a repository connection.) If a file that is used by a package in the Wise
Software Repository is added, the Files in Repository dialog box appears and prompts
you to add a version of the file that is in the repository.
See
Adding Files From the Wise Software Repository
on page 133.
The files that were accessed by the source application are added to the Files page. If you
use this information as a starting point for developing a complete installation, compile
and test the installation thoroughly to verify that it operates correctly.
Warning
Some of the files that are listed on the Files page might be platform-specific or non-
distributable Windows system files. If you are not sure whether it is safe to deploy a file,
check with Microsoft developer documentation before deploying these files to end users.
Convert SMS Installer or WiseScript Installation
Use the Convert SMS Installer or WiseScript Installation tool to convert the following
types of setup programs into Windows Installer packages:
z
Microsoft SMS (.IPF or .EXE)
z
WiseScript (.WSE or .EXE)
See
Converting an SMS Installer or WiseScript Installation
on page 394.
Conversion Guidelines
Following are guidelines for using Convert SMS Installer or WiseScript Installation:
z
You cannot convert all .EXEs—only those that were created with Microsoft SMS or a
WiseScript-based product.
z
If you do not have the original installation project file, you can convert the compiled
.EXE instead, because it contains an embedded copy of the script.
z
Because script installations are based on a different technology than Windows
Installer, not all elements of the script are converted to Windows Installer format.
Only the installation of files, registry changes, and other system changes are
converted.
Custom dialog boxes, custom logic, and other settings are not converted.
z
All the files that are available to the original installation must be available to the
converted Windows Installer package at the same locations.
z
Components are converted to features, and Execute Program script actions are
converted to Execute Program custom actions.
z
Some script actions can cause problems with the conversion process.