 |
 |
| |
|
|
Merge modules are essentially simplified .msi files, which is the file name extension for a Microsoft® Windows® Installer installation package. A standard merge module has an .msm file name extension.
A merge module cannot be installed alone because it lacks some vital database tables that are present in an installation database. Merge modules also contain additional tables that are unique to themselves. To install the information delivered by a merge module with an application, the module must first be merged into the application's .msi file.
Microsoft Merge Modules
Microsoft provides many precreated merge modules that you can add to your setup.
You can download them here: Windows Installer Merge Modules Download - English
After extracting them you'll have many msm files.
Just to list some of them:
mfc42.msm
mdac.msm
oleaut32.msm
tabctl32.msm
msvcrt.msm
msvbvm60.msm
...
THBComponentware Merge Modules
You can download our merge modules here: Windows Installer Merge Modules Download
Distributing ActiveX controls or COM objects
ActiveX controls and COM objects require up to date ole files installed on the system.
Therefore it is necessary to add the 'oleaut32.msm' to your setup in addition to the
control msm file itself.
Distributing .NET controls or COM objects
.NET controls don't need additional files and it is sufficient to add the control msm file.