Tim Titus

<div>
Thanks, the link was valuable!
</div>


<div>
<div class="content wysiwyg-content">
With InstallShield installations, why is it a good idea to separate all DLLs into individual separate components versus putting all DLLs in the same component?<br />
I have a consultant who created an installer where every registry entry, every file has a unique component associated with it and I'm trying to learn why this would be a good idea.
</div>
</div>


With InstallShield installations, why is it a good idea to separate all DLLs into individual separate components versus putting all DLLs in the same component?
I have a consultant who created an installer where every registry entry, every file has a unique component associated with it and I'm trying to learn why this would be a good idea.

InstallShield Separate Components for all DLLs

Installation is the act of making a computer program program ready for execution. Because the process varies programs often come with a specialized program responsible for doing whatever is needed for their installation. Installation may be part of a larger software deployment process. Cross platform installer builders that produce installers for Windows, Mac OS X and Linux include InstallAnywhere, InstallBuilder and Install4J. Installers for Microsoft Windows include Windows Installer, InstallShield, and Wise Installation Studio; free installer-authoring tools include NSIS, IzPack, Clickteam, InnoSetup, InstallSimple and WiX. Mac OS X includes Installer, and also includes a separate software updating application.