Validating a project involves applying a set of internal consistency evaluator (ICE) rules to your installation or merge module package. The ICEs are designed to help you determine whether the package contains a valid database that performs its actions correctly. If a package fails one or more ICEs, InstallShield reports the specific ICE rules that were violated and offers additional information to help you troubleshoot the problem.
Microsoft created many of the ICEs that are available in InstallShield; Acresso created the custom InstallShield ICEs (ISICEs) that are available for the InstallShield Certified for Windows Vista Validation Suite and the InstallShield Certified for Windows Vista Merge Module Validation Suite. The ISICEs help you validate your package against best practices for Windows-based installations.
Windows Logo Guideline
Validating your project may help you identify whether your installation meets installation requirements for Microsofts Certified for Windows Vista program. Therefore, if you are interested in being able to use the Certified for Windows Vista logo, it is recommended that you use the InstallShield Certified for Windows Vista Validation Suite and the Full MSI Validation Suite to validate your installation package. If you create a merge module in InstallShield, use the InstallShield Certified for Windows Vista Merge Module Validation Suite and the Merge Module Validation Suite to validate your merge module. For more details, see.
To learn more about the Certified for Windows Vista program, visit.
The InstallShield Premier Edition includes a set of validators called the InstallShield Best Practice Suite. The InstallShield Best Practice (ISBP) validators in this suite alert you if your installation violates best-practice guidelines.
InstallShield also provides an engine for upgrade and patching validation. You can access this through the Upgrade Validation Wizard.
Copyright Information | Contact Acresso