tlbimp is correct. In addition, you will have to Add a reference to the
interop assembly from your application.
When using tlbimp, you can create a new file name to distinguish between
the COM+ DLL and the Interop Assembly.
For example:
tlbimp.exe MyComPlus.dll /out: InteropMyComPlus.dll
hth
Jekke Bladt <[EMAIL PROTECTED]>
Sent by: "Moderated discussion of advanced .NET topics."
<[EMAIL PROTECTED]>
12/11/2003 01:02 PM
Please respond to "Moderated discussion of advanced .NET topics."
To: [EMAIL PROTECTED]
cc:
Subject: Re: [ADVANCED-DOTNET] COM+ DLL and Managed C++
Charles Gamble wrote:
> We have a set of VC6 ATL COM+ objects. We want to expose these
> natively as .NET objects.
> Can we simply convert the VC6 projects to VC7, change the build to
> support managed extensions and add a C++ CLR managed class that passes
> on method calls to our ATL COM+ object?
Charles--
In order to call your COM dll from .net, you need to generate a RCW
(runtime callable wrapper) using a .net utility that I believe is called
tlbimp. The RCW is a .net assembly that will emulate the interface of
your COM-based classes. You will not have to recompile your COM
component and you will be able to deploy the COM DLL and the RCW
side-by-side.
--Jekke
--
NOTICE: If received in error, please destroy and notify sender. Sender
does not waive confidentiality or privilege, and use is prohibited.
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
Some .NET courses you may be interested in:
NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles
http://www.develop.com/courses/gaspdotnetls
View archives and manage your subscription(s) at
http://discuss.develop.com
===================================
This list is hosted by DevelopMentorŪ http://www.develop.com
Some .NET courses you may be interested in:
NEW! Guerrilla ASP.NET, 26 Jan 2004, in Los Angeles
http://www.develop.com/courses/gaspdotnetls
View archives and manage your subscription(s) at http://discuss.develop.com
