Deployment in Visual Studio-Merge Module Project)

Deployment in Visual Studio

Merging module Introduction

(Http://technet.microsoft.com/zh-cn/magazine/6771e4ch (vs.90). aspixel)

The merging module is a function of Windows Installer. It provides a standard method for transferring components to ensure that the correct version of the component is installed. The merging module contains components such as. dll and any related files, resources, registry items, and installation logic.

The merging module cannot be directly installed, but is merged into each application using the component.Program. This ensures that components are installed for all applications in a consistent manner, eliminating version conflicts, loss of registry keys, and incorrect File Installation.

Each merge module contains a unique version information. The Windows Installer database determines the application that uses the component through this information to prevent the component from being removed too early. Therefore, a new merging module should be created for each incremental version of the component. The merging module should be included in the installation program and should never be updated.

With the deployment tool in Visual Studio, you can easily create and include modules in the installation program of the application.

 

Installer and merging module: Differences and Suggestions

(Http://technet.microsoft.com/zh-cn/magazine/y0w2est5 (vs.90). aspixel)

Visual Studio allows you to create two different types of Installer: Windows Installer (. MSI) and merge module (. MSM ). Windows Installer is used to install applications and files on other computers. The merging module is used to install components shared by multiple applications.

The main difference between the two types is that the target user objects are different. End users of the application package all the content (executable files, documents, HTML pages) directly used in Windows installer. Any content (DLL, control, and resource) for developers only should be packaged into the merging module, developers can then package the modules to the end user's Windows installer.

In general, any component shared (or possibly shared) by multiple applications should be put into its own merging module. Although multiple components can be put into one merging module, it is better to create a merging module for each component to avoid distributing unnecessary files.

The merging module is similar to a snapshot of a specific version of the component. To avoid version conflicts, create a new merging module for each subsequent version of the component.

The installer can contain multiple applications, allowing you to install one set of applications in one step. In this case, the installer should include the merging modules of all components used by the included applications. If a merging module is used by multiple applications, it only needs to be added once.

 

How to: Add a merging module to a deployment project

(Http://technet.microsoft.com/zh-cn/magazine/8x727h8b (vs.90). aspixel)

The merge module (. MSM file) allows you to share components between multiple deployment projects. You can use Visual Studio to create your own merging modules, or use existing merging modules provided by Microsoft and third-party vendors that can be used for many standard components.

Add a merging module to a deployment project

1. In Solution Explorer, select a deployment project.

2. On the "project" menu, point to "add" and click "Merge Module ".

3. In the "add module" dialog box that appears later, browse to the location of the merging module to be added.

 

From:

Crystal Reports merging module of Visual Studio 2005

Http://technet.microsoft.com/zh-cn/library/ms225293 (V = vs.80)

Http://technet.microsoft.com/zh-cn/library/ms225386 (V = vs.80)

How to: create or add a Merge Module Project

Http://technet.microsoft.com/zh-cn/library/z6z02ts5 (V = vs.80). aspx

. NET application package deployment Summary

Http://lib.open-open.com/view/open1339657958974.html

"Merge Module" Project

Http://technet.microsoft.com/zh-cn/library/0h4bhcz3

Http://technet.microsoft.com/zh-cn/6771e4ch (vs.71). aspx

Http://technet.microsoft.com/zh-cn/magazine/8x727h8b (vs.90). aspx

Http://technet.microsoft.com/zh-cn/magazine/y0w2est5 (vs.90). aspx

Http://technet.microsoft.com/zh-cn/library/0h4bhcz3

Http://www.doc88.com/p-706876760738.html