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.

Labels:

Comments

Post a Comment

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...
Post a Comment
Continue Reading »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »