Merge module vs Sharing dll
Hi friends,
I am studying the difference between sharing any dll/incrementing dll count and using merge module for that perticular dll, Please share your thoughts.
My understanding is, (may be I am wrong), if we are sharing dll then only that perticular dll's count gets increased and at the time of uninstallation if it is still in use, then that dll remains, but other objects in that component gets removed, but in case of merge module it retains whole merge module component, after uninstallation as well, if it is still in use.
I am studying the difference between sharing any dll/incrementing dll count and using merge module for that perticular dll, Please share your thoughts.
My understanding is, (may be I am wrong), if we are sharing dll then only that perticular dll's count gets increased and at the time of uninstallation if it is still in use, then that dll remains, but other objects in that component gets removed, but in case of merge module it retains whole merge module component, after uninstallation as well, if it is still in use.
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
AngelD
14 years ago
Yes, shared dll uses a single file counter while a component (within a merge module or not) has it's own reference counter and will remove all resources (files, registry, ini...) if only one package installed the component.
Posted by:
abking99
14 years ago
Where can I find out information, about mechanism of merge module? How exactly does it work?
Posted by:
anonymous_9363
14 years ago
Where can I find out information, about mechanism of merge module
Posted by:
abking99
14 years ago
why this smiley? if you want to learn something in deep, is it wrong? overall we all know how it works, but i wanted to know backend mechanism....
Posted by:
anonymous_9363
14 years ago
why this smiley?Seriously, what do you expect? How many times will you have to read the entreaty to use Google before the message sinks in? If you're expecting an in-depth tutorial here, you're seriously deluded. Besides anything else, who has the time?
Google MSDN and TechNet. If the information you find there isn't sufficient, you'd probably need to speak to a Microsoft lead developer in person.
Posted by:
abking99
14 years ago
I already mentioned that I am also studying on it, and I needed input of other packagers, who knows these concept better. Anyways If you have any contact details of Microsoft's lead developer, then please share with me
Posted by:
timmsie
14 years ago
Anyways If you have any contact details of Microsoft's lead developer, then please share with me
hehe it's like clueless all over again!
Posted by:
pjgeutjens
14 years ago
Ok, abking, I'm in a good mood since my new server arrived yesterday, so..
http://msdn.microsoft.com
in the search windows type in "Merge Module"
top link
This took me less than 30 seconds to find...
PJ
http://msdn.microsoft.com
in the search windows type in "Merge Module"
top link
This took me less than 30 seconds to find...
PJ
Posted by:
ghosh.kunal
14 years ago
The main thing with Merge Modules is that it provides for consistent components, that is same component GUIDs for the same set of DLLs. You might have the same version of DLL in 2 different MSIs with different component GUIDs, which would not help DLL Hell situation, because windows installer would check for components (Using Component GUIDs) and not files.
Thats why Merge Modules are always preferred over incrementing the DLL reference counts.
Thats why Merge Modules are always preferred over incrementing the DLL reference counts.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.