Welcome Panel
InstallShield 2025 » Setup Best Practices Wizard
The wizard is informing you that by adding files to a component you have violated one of the following Setup Best Practices:
|
Best Practice |
Description |
|
Components Should Not Contain Multiple EXEs, DLLs, OCXs, CHMs, or HLPs |
Each component should contain only one “portable executable” file (an EXE, DLL, or OCX) or help file (CHM or HLP). Windows Installer components are designed such that all of the advanced settings and component properties, such as the code GUID, refer ideally to a single portable executable or help file. Place other EXEs, DLLs, OCXs, CHMs, or HLPs into new components. |
|
A File Cannot Be Associated with More than One Component |
This Best Practice is extremely important for shipping reusable components and facilitating resiliency. Microsoft recommends that no file be shipped in more than one component, “even across products, product versions, and companies.” |
|
Use Merge Modules |
Merge modules contain all of the files, registry entries, and logic necessary to install a distinct piece of functionality. You should not distribute a file for which a merge module is available. Using merge modules also helps you comply with two related requirements—the Best Practice to avoid associating a file with more than one component and the Windows logo guideline not to ship any core components. If the Best Practices monitoring option is enabled, the Setup Best Practices Wizard alerts you whenever you try adding to a component any file that is part of the merge modules that InstallShield provides. |
Panel Options
Please do not warn me of other Setup Best Practice conflicts
Selecting this option if you do not want the Setup Best Practices Wizard to notify you of Best Practices violations. You can reverse this action later in the Tools | Options panel.