Windows Installer Editor Reference
408
Tools
z
Component design
Checks that the proper files have been placed into each component and that the
same file has not been placed into multiple components.
z
Uninstall support
Checks that the package does not reference non-Windows Installer uninstall
utilities.
z
Files in shared folders
Checks that no executable files have been placed in shared directories.
z
Hidden and protected application files
Checks that application files have been protected from accidental deletion by the
end user.
z
Transitive flag set on OS based components
Checks that the Transitive bit is set on operating system-dependent components.
Transitive components are components that must be swapped out if the end user
upgrades the destination computer to a new operating system.
z
Icon placement in Start Menu
Checks that shortcut icons are installed correctly in the Start Menu.
z
All application/library files are 32-bit
Checks that no 16-bit components are included in the package.
z
Changes to Win.ini or System.ini
Checks to see if changes are being made to these files.
z
Components shared with non-Windows installer applications
Checks that no components of the package are shared with other applications that
do not use Windows Installer.
z
Files installed to Program Files by default
Checks that all application files are installed to a subdirectory of Program Files.
z
Terminal Server Compatibility
Checks for errors that might cause problems when the package is installed in a
Microsoft Terminal Services or Citrix environment. With terminal service
applications, installation resources must reside in per-machine locations rather than
per-user locations. Errors result from this test if the installation is set to install per-
user, if any keypaths reside in user-specific locations, or if environment variables
are present in the installation. If environment variables are present, using the
Correct button duplicates the variables, creating a per-user set and a per-machine
set, one of which is installed depending on the value of ALLUSERS. Correcting some
errors might cause keypaths to be empty, and might cause a one-time repair. You
can set a release to be compatible with Terminal Services. See ALLUSERS Property
in the Windows Installer SDK Help.
See also:
the description of the Release Type field in
Creating a New Release
on page 207
See also:
Validating a Package
on page 404
ICE Reference in the Windows Installer SDK Help
Merge Module ICE Reference in the Windows Installer SDK Help
Windows Vista/Windows 7 Validation
on page 409
Customizing Validation Modules
on page 406