Merge Module Practices
Posted 14 November 2011 - 16:31
I want to know when one should use the merge modules.
for e.g; there is a merge module for atl71.dll and I can also directly link that file in a separate component .So whether I should use the merge module provided by Installshield or I should link the file directly by creating a new component for it.
In one link I read :
"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. "
Posted 15 November 2011 - 20:36
Posted 17 November 2011 - 15:45
Posted 21 November 2011 - 22:45
I am confused whether to create a merge module to pick these files or to create separate components. Please help
Posted 22 November 2011 - 17:27
The files will be used privately.But there are still few doubts :
1. There are bunch of dlls so should I put all of them into single component or maintain different components for each files.But then where would I be putting the manifest file??
2. After adding the dlls into the component,do I need to add information into Advanced Settings->Assemblies?
3. I tried creating a single component for bunch of dlls and when I was adding information of "File Application" in Component->Advanced Settings->Assemblies
It set the path automatically to [INSTALLDIR]atl71.dll.So should I consider this setting for the rest of the dlls as well or this particular setting is only for atl71.dll.