User Guide

370
Package Validation
Package Validation
Package Validation checks a Windows Installer package for errors based on rules in one
or more validation modules. It validates package files (.MSI and .WSI), merge modules
(.MSI and .WSM), and transforms (.MST). For details, see Validating a Package.
! If you correct validation errors in a .WSI or .WSM, it is recompiled to an .MSI or
.MSM at the end of validation.
! If you correct validation errors in an .MSI or .MSM, errors are not corrected in any
corresponding .WSI or .WSM.
! When you specify a transform, Package Validation checks both the transform and the
original .MSI.
Package Validation contains predefined validation modules. See Predefined Validation
Modules on page 378. In the Professional and Enterprise Editions, the validation
modules are fully customizable to accommodate corporate standards:
! You can select which validation rules to use during the validation test.
! You can create new validation modules and new validation rules. (Enterprise Edition
only.)
See Customizing Validation Modules on page 372.
Portions of Package Validation were developed based on public Microsoft documents. It
has not been reviewed or certified by Microsoft. This tool helps you prepare a package
for certification, but cannot guarantee that the application will meet all Windows
Application Specification requirements. For information on Windows requirements, see
Windows Installer and Logo Requirements in the Windows Installer SDK Help.
Note
Package Validation ignores issues pertaining to the group box “enabled” attribute, which
Microsoft’s validation module falsely reports as an error.
Validating a Package
Use Package Validation to verify an installation package using predefined or customized
validation modules.
1. Open the installation file (.MSI or .WSI), merge module (.MSM or .WSM), or
transform (.MST) to test.
2. Select Tools menu > Package Validation. (In Visual Studio: Project menu > Package
Validation.)
The Welcome dialog appears.
3. To view the description of a validation module, select the module in the list.
4. Mark the validation modules to use to validate the package.
By default, the list contains predefined validation modules. See Predefined
Validation Modules on page 378.
Note
The tests in Application Specification Logo are a subset of the tests in Internal
Consistency, therefore, running both tests at the same time might result in duplicate
errors.