InstallShield 2018
Use the following guidelines to separate an application into components.
| • | Identify resources that function as a group; each group can be a component. |
| • | Windows Installer requires that every file in a component be installed to the same directory. If you need to install a directory structure, each subdirectory must correspond to a separate component. |
| • | The resources in a component should require the same conditions. |
| • | To take full advantage of Windows Installer repair functionality, each .exe, .dll, and .ocx file should be placed in its own component, and each should be the component’s key file. The Best Practices option of the Component Wizard can create components for you using this rule. |
| • | Similarly, each .chm or .hlp file should be placed in its own component, along with any corresponding .chi or .cnt file. |
| • | No resource should be included in more than one component, even across products. If a component’s resources are required by more than one product, consider creating a merge module with the shared resources. |
| • | When mapping a component to one or more features, ensure that all parts of a component map to the features. |
| • | When testing your installation, you may want to divide your application into several components to thoroughly measure its performance. |
See Also
InstallShield 2018 Help LibraryJanuary 2018 |
Copyright Information | Flexera |