| A .NET remoting object is generally deployed with the server application that uses it. This server application can be created as a console application, a Windows application, a Windows service, or a Web application. Based on what you have studied so far, the process of deploying a .NET remoting object is very similar. Components such as serviced components and .NET remoting objects can be shared between multiple applications. You might want to distribute these components to be used by other developers as part of their applications. The process of packaging a component for reuse in other applications is different from packaging a Windows application for deployment. When you have a component that will be shared among multiple applications, you should package it as a merge module (.msm file). A merge module includes the actual component, such as a .dll file, along with any related setup logic, such as resources, Registry entries, custom actions, and launch conditions. Merge modules cannot be installed directly. They need to be merged with the installation program of an application that uses the shared component and packaged into a merge module. When you modify a component to release new versions, you create a new merge module for each of the new versions. A new merge module should be created for each successive version of a component, to avoid version conflicts. | 
