All,
I am aware that using merge modules for your common system dll's, like tabctl32 and comctl32, is the way to go when packaging and deploying to an environment. Now I was hoping to put a white paper together to describe the benefits and reasons to use merge modules however find information around the net is hard, guess im not using the correct search words!

Can anyone point me in the right direction for the benefits in both cost and time to using merge modules, or the reasons that I shouldnt use them?

Regards,
Paul
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Are you talking about patching? Like with MSP files or EXE's? Just wanted to make sure we are talking about the same thing.
Answered 09/21/2007 by: yarborg
Blue Belt

Please log in to comment
0
Im talking about taking common DLL's, OCX's etc and creating a merge module from them and then storing them in a central location for a department to use.

The idea being that instead of a vendor or repackaged MSI using their own install files they would, if the file was there, switch to using the merge module in the central location.
Answered 09/21/2007 by: Inabus
Second Degree Green Belt

Please log in to comment
0
The advantage of using merge modules is that the components will have the same GUID. So when two packages use the same merge module it uses the component sharing mechanism correctly. Otherwise 2 packages could place the same file in for instance the %WinDir% with different components, but the sharing in that case can only be controlled by the shareddll counter, not the component counter because the GUIDs dont match.

Sorry I have to go now, but if you need more in depth or better explained info, let me know. I will make a bigger post.
Answered 09/21/2007 by: FrankSpierings
Orange Senior Belt

Please log in to comment
0
Well my reasons for asking is to understand the pro's and con's so that I can produce a white paper to give to my boss to say "you should use merge modules and not just ignore them.

What im also after is cost savings, which I am sure there is, with using them, although I know there would be an initial cost to get the modules created in the first place.

Thanks for the information you posted already, dont suppose you have any links to MS etc that say "here is what merge modules are and why to use them"? I have done my best to try and google this but not found much so far.



Paul
Answered 09/24/2007 by: Inabus
Second Degree Green Belt

Please log in to comment
0
I recall researching this a while ago when I was at a client who said "Thou shalt NOT use merge moduls" and found differing opinion from within MS. IIRC, this was on MSDN blogs/webcasts but don't quote me...
Answered 09/24/2007 by: VBScab
Red Belt

Please log in to comment
0
Yeh im in the same boat now, we dont use them, although they cant say why and wanted a white paper produced for why we should use them. Thats what im in the process of trying to get together now:

http://blogs.msdn.com/robmen/archive/2003/10/04/56479.aspx

The above link is looking good so far :)

P
Answered 09/24/2007 by: Inabus
Second Degree Green Belt

Please log in to comment
0
Just curious to know if you have created the white paper, It could be helpful.
Answered 05/26/2009 by: ghosh.kunal
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity