Merge Module
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Merge Module" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Merge Module|concern=Fails [[WP:NSOFT]]}} ~~~~Timestamp: 20250301174426 17:44, 1 March 2025 (UTC) Administrators: delete |
 | This article needs additional citations for verification. (February 2013) |
A merge module is a special kind of Windows Installer database that contains the components needed to install a discrete software bundle.[1] A merge module cannot be installed alone, but must be merged into a standard Windows Installer installation during the creation of the installation. Typically, a merge module or a collection of merge modules related by dependencies, installs a software product or portion of a product at runtime. The purpose of merge modules is to let you add self-contained software modules to multiple installations.
For example, if there are a number of applications that require a specifically configured component, it would be possible to create a merge module that installs and configures that component. That merge module could then be added to the installation packages of each product that required that particular component. This saves the effort of having to individually add the necessary files, registry entries, and other components to every installation. It also saves time if updates are needed, as instead of updating the installations for all applications, only the merge module is updated, and the installations only need to be rebuilt.
Standard merge modules have a .msm file extension.[1] Some merge modules may be configurable merge modules. Such merge modules contain certain values that can be set to specify how the module behaves in your installation. For example, the author of the configurable merge module may allow attributes to be set on components, enable or disable isolated components, specify a bitmap for a dialog, or specify how a custom action is run. Configurable merge modules are supported only by Windows Installer 2.0 or higher.[2]
There exist a number of pre-created merge modules which install commonly used Microsoft software packages, such as MDAC, ActiveX controls, MFC, SAPI and DCOM.[citation needed]
References
- ^ a b "Merge Modules documentation on Dev Center". Retrieved 5 September 2012.
- ^ drewbatgit (7 January 2021). "Configurable Merge Modules - Win32 apps". docs.microsoft.com. Retrieved 2022-08-18.
 | This Microsoft Windows article is a stub. You can help Wikipedia by expanding it. |