Export (0) Print
Expand All
1 out of 1 rated this helpful - Rate this topic

Registration-Free COM Interop

Registration-free COM interop activates a component without using the Windows registry to store assembly information. Instead of registering a component on a computer during deployment, you create Win32-style manifest files at design time that contain information about binding and activation. These manifest files, rather than registry keys, direct the activation of an object.

Using registration-free activation for your assemblies instead of registering them during deployment offers two advantages:

  • You can control which DLL version is activated when more than one version is installed on a computer.

  • End users can use XCOPY or FTP to copy your application to an appropriate directory on their computer. The application can then be run from that directory.

This section describes the two types of manifests needed for registration-free COM interop: application and component manifests. These manifests are XML files. An application manifest, which is created by an application developer, contains metadata that describes assemblies and assembly dependencies. A component manifest, created by a component developer, contains information otherwise located in the Windows registry.

Requirements for Registration-Free COM Interop

Identifies operating system and .NET Framework version requirements.

Configuring COM Components for Registration-Free Activation

Describes COM side-by-side assemblies.

How to: Configure .NET Framework-Based COM Components for Registration-Free Activation

Describes how to create an application manifest and how to create and embed a component manifest.

Side-by-Side Execution for COM Interop

Describes how to safely share components through COM interop services.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.