"Old" COM compatibility - Permission to beat me if this is a bad question is granted

  • Thread starter Thread starter Rich Wallace
  • Start date Start date
R

Rich Wallace

Hi all,

Please forgive me if this has been answered already, I looked around the
group and I couldn't find anything that jumped out at me.

We utilize Informatica in our environment as an ETL tool for a Data
Warehouse solution. I currently develop most of our custom solutions in
VB.NET that may be utilized by a COM+ call such a BizTalk Server or other
custom application.

We are trying to develop an Informatica solution that will connect to a use
a custom COM DLL that I have written but the Informatica side will only
recoginze VB6 DLL's that I have in place, it looks for the TypeLib entry in
the registry related to the CLSID in the registry for the component it's
linking to.

Is there a way I can still develop the COM components in .NET, and make them
compatibile with the old style of VB6 COM development so that our custom
Informatica solution will recognize it?

TIA
-Rich
 
Hi all,

Please forgive me if this has been answered already, I looked around the
group and I couldn't find anything that jumped out at me.

We utilize Informatica in our environment as an ETL tool for a Data
Warehouse solution. I currently develop most of our custom solutions in
VB.NET that may be utilized by a COM+ call such a BizTalk Server or other
custom application.

We are trying to develop an Informatica solution that will connect to a use
a custom COM DLL that I have written but the Informatica side will only
recoginze VB6 DLL's that I have in place, it looks for the TypeLib entry in
the registry related to the CLSID in the registry for the component it's
linking to.

Is there a way I can still develop the COM components in .NET, and make them
compatibile with the old style of VB6 COM development so that our custom
Informatica solution will recognize it?

TIA
-Rich
Click to expand...

Basically, you need to use tlbexp to create a typelibrary from your .NET
library and then you can register the component as a COM component.

Not an area, I've really had to deal with - but I think the IDE can do
this for you. I think there is a project property that gives you the
option to develop for COM interop...

Anyway, maybe someone can give you more specific details if you have
further questions :).
 
Also try asking in the "interop" newsgroup - as they deal with these kind of
questions all the time ;)

microsoft.public.dotnet.framework.interop
 
Awesome, thank you!

Robin Tucker said:
Also try asking in the "interop" newsgroup - as they deal with these kind of
questions all the time ;)

microsoft.public.dotnet.framework.interop
Click to expand...
 
Back
Top