Library tutorials & articles
COM Interoperability in .NET Part 2
Introduction
This article elucidates how to build and install-managed code that will be used from COM applications. A classic COM server is activated using the Service Control Manager (SCM). It looks up numerous information such as CLSIDs, IIDs, ProgIDs etc.
So what is the solution to use the .NET assemblies in the classic COM clients,
These are the steps concerned in the build process are as follows:
- Write and compile the managed code.
- Generate a COM type library (*.tlb) for the assembly using the tlbexp.exe
utility so that allow the COM client to interact with the exposed types.
- Install and register the assembly so that COM SCM to locate it.
- Write and compile the COM code that references types in the assembly.
For demonstration purposes, I have created a .NET component in C# named Calculator. For client side, I have created a Visual Basic (VB) 6.0-based client.
Related articles
Related discussion
-
Are Native code making a comeback ? I think it never went away
by JoeGecko (0 replies)
-
Socket Programming in C# - Part 1
by graumanoz (23 replies)
-
Creating a Windows Service in VB.NET
by Templario55 (107 replies)
-
C# Windows Application Problem in Dynamically generated control
by BAmoozad (1 replies)
-
The Future of .NET Languages
by hack2root (2 replies)
Related podcasts
-
More jQuery in ASP.NET
In this episode Chris Brandsma, Rick Strahl, Dave Ward, Bertrand Le Roy, and Scott Koon conclude their discussion of Microsoft's jQuery in ASP.NET announcement1.This episode of the Alt.NET Podcast is brought to you by LLBLGen Pro, the most mature O/R mapper and code generator out there.Are ...
Events coming up
-
Nov
18
15 Minutes of Fame
Dresher, United States
This is a yearly tradition. We select 10 of the favorite speakers from monthly meetings, code camps, and hands on labs. Each one does a 15 minute talk on their favorite .NET technology. This is our 10th anniversary so we plan a gala event with special prizes and refreshments.
I AM A CHINESE,THIS IS MY FIRST TIME TO VISIT THIS WEB SITE~~~~
I MAJOR IN COMPUTER,SOFTWARE,BEING A SOPHIMORE ,I AM SO DESIRABLE TO MAKE A FRIENDS WITH DIFFERENT COUNTRIES~~~~~
I LIKE SPORTS,ESPECIALLY BASKETBALL,AND MUSIC,PLAYING GUITAR~~~~~~
I LOOK FORWARD TO RECEIVING YOUR MESSAGE,MY EMAIL:CHARLES_ANDREW@163.COM
THANKS ,A FRIEND FROM CHINA
Hello, good news!!!
I just figured out what was missing in what was reported in previous comment.
In the Properties Pages of the .NET project, choosing "Configuration Properties" on the left panel, and then "Build", there is a switch labelled "Register for COM Interop", and of course it has to be set "ON", for all this to work as expected!!!!
Well, let's keep working.!!!!
Be well!!!!!
Hello, G.Gnana Arun:
Hi, good day, greetings from Mexico City.
Well, this post is to commet I just tried your implementation, I created a .NET DLL with VB.NET, then followed the .TLB file, just as you specify in your article, but at the moment of using the library in a VB 6.0 project, using the reference to the .TLB file, as you dictate, just when the object is to be instantiated, I receive a Num 429 error, "ActiveX Object can“t be created". I include here the code for the class in VB.NET:
Public
Class cDotNetUtilsVB60 Public Shared Function IsPositiveInfinity(ByVal pdblNum As Double) As Boolean Dim lnuNumTem As Double Return lnuNumTem.IsPositiveInfinity(pdblNum) End Function Public Shared Function IsNegativeInfinity(ByVal pdblNum As Double) As Boolean Dim lnuNumTem As Double Return lnuNumTem.IsNegativeInfinity(pdblNum) End FunctionEnd
ClassCan you figure out what I'm doing wrong???????
Thanks in advance, be well
Roberto Gutierrez R.
This thread is for discussions of COM Interoperability in .NET Part 2.