COM+ Interop

[Guest]

I have a COM+ component developed in C#. Can I use this from VB6 client ? Any
issues with doing this. This component has a lot of business logic and is
being used by other C# and ASP.Net clients. Thanks

 

[Willy Denoyette [MVP]]

I have a COM+ component developed in C#. Can I use this from VB6 client ?
Any
issues with doing this. This component has a lot of business logic and is
being used by other C# and ASP.Net clients. Thanks

If your COM+ component is designed to be COM "friendly" this shouldn't be a
problem.

Willy.

 

[Nicholas Paldino [.NET/C# MVP]]

O'Neil,

No, it shouldn't be a problem. The big thing is that you should have
separated interface from implementation. If you did that, then it's very
easy. You can just call CreateObject, passing the program id of the COM+
component, and then cast to the interface (which you can create using the
TLBEXP utility to create the type library).

Hope this helps.

 

[Willy Denoyette [MVP]]

Note that the typelib is created when running the regsvcs.exe utility, which
is required to register the component in the COM+ catalog.

Willy.

O'Neil,

No, it shouldn't be a problem. The big thing is that you should have
separated interface from implementation. If you did that, then it's very
easy. You can just call CreateObject, passing the program id of the COM+
component, and then cast to the interface (which you can create using the
TLBEXP utility to create the type library).

Hope this helps.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

I have a COM+ component developed in C#. Can I use this from VB6 client ?
Any
issues with doing this. This component has a lot of business logic and is
being used by other C# and ASP.Net clients. Thanks