I've used them in most places i've worked, but what are the advantages so that i can try and get the company i work with presently to use them.

From what i understand they standardise shared components and reduce the risk of conflicts between apps.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Correct, I guess you can find pros and cons on the Wise web site?
Answered 09/15/2004 by: fetgor
Senior Purple Belt

Please log in to comment
Merge modules do a few things but the important parts are...

1) Shared DLLs: When using merge modules for common DLLs it prevents you from uninstalling a common DLL that another application might need. The other application needs to have the DLL count registered for the DLL as well otherwise the DLL will be installed regardless. Now this should not be a big deal if the advertising info exists in the other application's MSI as it should detect and self heal the MSI when a call is made for the DLL.

2) Simplifies nasty installs: I guess the big one is BDE as you don't want to setup capture different BDE configurations then install them on the same machine. By using a merge module it ensures that the BDE engine is installed correctly and configured correctly effectively eliminating conflicts.
Answered 09/15/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment