InstallShield 2015
The InstallShield validation suites consist of a number of InstallShield ICEs (ISICEs) that help you check your project for compliance with installation requirements of the Windows logo program.
The following table lists the ISICEs that are available in InstallShield.
|
ISICE |
Project Type |
Description |
|
Basic MSI, |
Validates that the application is installed to ProgramFiles or the user’s AppData folder by default. |
|
|
Basic MSI, |
Validates that all executable files included with the installation or merge module are digitally signed. |
|
|
Basic MSI, |
Validates that there are no nested-installation custom actions (type 7, 23, and 39). |
|
|
Basic MSI, |
Validates that there are no custom columns added to standard .msi tables. |
|
|
Basic MSI, |
Validates that there are no properties or custom tables that begin with MSI (case-insensitive). |
|
|
Basic MSI, |
Validates that the installation does not include any files protected by Windows Resource Protection. |
|
|
Basic MSI, |
Validates that MSI components are authored for proper installation and uninstallation. |
|
|
Basic MSI, |
Validates that deferred custom actions do not have the impersonate bit set. |
|
|
Basic MSI, |
Validates that the installation includes an MsiPatchCertificate table entry. |
|
|
Basic MSI, |
Validates that each custom action has a path specified for the Help File Path setting in the Custom Actions view. |
|
|
Basic MSI, |
Validates that .exe files have embedded manifests with required information. |
|
|
Basic MSI, |
Validates that no protected registry keys are modified. |
|
|
ISICE13 |
Basic MSI, |
Validates that no .hlp files or WinHelp run-time files are included in the installation. This ICE is now ISBP17. |
|
ISICE14 |
Basic MSI, |
Validates that no obsolete APIs are imported. This ICE is now ISBP18. |
|
ISICE15 |
Basic MSI, |
Validates that no deprecated APIs are imported. This ICE is now ISBP19. |
|
Basic MSI, |
Validates that no 16-bit components are distributed in an installation that targets 64-bit systems. |
|
|
Basic MSI, |
Validates that the installation or merge module does not force a reboot. |
|
|
Basic MSI, |
Validates that the MsiRMFilesInUse dialog is included. |
|
|
Basic MSI, |
Validates properties related to upgrades, that the Upgrade table is present, and that the installation prevents downgrades. |
|
|
Basic MSI, |
Validates that no machine-wide settings are installed by a non-privileged installation. |
|
|
Basic MSI, |
Validates that the app does not depend on the VB6 runtime. |
|
|
Basic MSI, |
Validates that the app does not start automatically on system startup. |
|
|
Basic MSI, |
Validates that the app sets strong and appropriate ACLs. |
|
|
Basic MSI, |
Validates that the installation does not install 16-bit components. |
|
|
Basic MSI, |
Validates that the installation does not install any files to the Windows directory or its subdirectories. |
|
|
Basic MSI, |
Validates that applications support Windows security features by controlling permissions appropriately. |
Tip: In some cases, the following validation error message may be displayed for an ISICE:
File [1] in Component [2] could not be found. All tests against this file's contents may be invalid.
This error occurs if the specified file is missing, and the associated ISICE could not be verified for the file. For example, if an executable file is missing, ISICE11 cannot verify whether the file has an embedded manifest.
If the aforementioned validation error message is displayed, resolve the missing file issue, and then rerun validation for your project.
See Also
InstallShield 2015 Help LibraryJune 2015 |
Copyright Information | Contact Us |