Skip to main content

COM Interoperability in .NET



Namespace: System.Runtime.CompilerServices

Why we need Interoperation?
A company may have a large application that is already tested, verified, and is stable. And they are interested to use new technology while keeping the old at its position.

Secondly, not every windows API has been wrapped in with .NET Framework.

.Net provides ample support for COM interoperation to import and use type libraries. Runtime Callable Wrapper (RCW) is used to bridge the communication between the COM and .NET.

Importing Type Libraries:
There are two ways to Import libraries.

1.       Using Add Reference Feature in Visual Studio 2005 and selecting appropriate COM component.
2.       Using tlbimp.exe. In command prompt go to the location where your assembly is, then execute the command “tlbimp.exe MyDll.dll [/out:ManagedMyDll.dll]

In C# optional parameters are not supported, so if you want to pass something as null, use Type.Missing. This is because COM Objects do not support parameter overloading, and they require you to pass in objects as a reference.

You can use: object obj = Type.Missing;

Tools used by COM Interop

TlbImp.exe (Type Library Import)
It imports a COM component to be consumed by the .Net Application.

TlbExp.exe
It exports a .Net Assembly sot that it can be consumed by the COM objects.

Regedit.exe
All COM components require to get registered in Registry, so it’s the right tool for them.

Ildasm.exe
Intermediate Language Disassembler to view intermediate language code.

Regasm.exe
It enables you to add/remove .NET assemblies from system registration database.


Handling Exceptions in COM Interop:
 In .Net framework 2.0, exceptions thrown from the .NET or from outside the .Net Framework are caught by catch (exception ex) {} as usual. But you should first look for the System.CompilerServices.RuntimeWrappedException, which have the property WrappedException that provides you the actual exception thrown outside the framework.

Limitations of the COM Interop:

Static/Shared Members: .Net framework does not support static/shared methods.
Parameterized Constructors: COM doesn’t allow parameterized constructors.
Inheritance: Shadowed members in COM component are not recognizable / callable.
Portability: COM components require registry that is not be available on platform other than windows.

Comments

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Exposing .NET Components to COM

Namespace: System.Runtime.CompilerServices Building .NET Components for use by COM .Net framework generates COM Proxies known as COM Callable Wrapper (CCW) to be used by COM. No matter how many COM clients consume a given managed object, .Net runtime will create a single CCW. Write down you class and before building it, Select the configuration form the project properties named “ Register for COM interop ”. Hiding public .NET Classes from COM To hide a class or member just use the following attribute: [ComVisible(true/false)] . Deploying COM-Enabled Assemblies :       Check the following necessaries before creating CCW: 1.        All class have default constructor (no parameter). 2.        Exposed Types should be public . 3.        Any member exposed should be public . 4.        Abstract classes will not b...

ASP.NET Working with Web Configuration Files

Our sites are configured based on hierarchy of XML configuration files. Machine.config is top level configuration file located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\machine.config These settings are framework level and common to all Windows, Console, Class Library, and Web application. Some of them could be overridden in Web.config while others are protected. Next in hierarchy is Root.config. It’s located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\web.config It contains default web server settings. Optionally one can add at root of all websites a web.config to provide general settings related to all sites. Optionally to provide more control on settings one can add web.config in each web site and for each folder in that web site. Processing the Configuration files:                       ...