Help: using an ActiveX DLL with VS .Net

[Nick Alexander]

I have a 3rd party application API that I have been using, which all
works in VB6. I have upgraded to Visual Studio .Net 2003, and am
struggling to get it to work. What I did was:

VB6: (This works fine)
Create an ActiveX DLL project.
Refer to the API's .tlb file.
Use the Implements statement to use the API's interface.
Register the DLL with RegServ32.
From within the 3rd party app, refer to my functionality with
DLLName.ClassName.

VS 2003 .Net: (This doesn't work)
Create a VB Control Library DLL.
Refer to the API's .dll file.
Use the Implements statement to use the API's interface.
I get an error that the entry point could not be found if I try to
register with RegServ32; I beleive this is because I shouldn't be
trying to register it.
I get no response when I refer to my functionailty within the 3rd
party app.

I have not yet got the procedural differences between COM and .Net, so
I have seen reference to using gacutil.exe to registering my assembly,
but when I do that, I get told that it doens't have a strong name, so
then I start looking at sn.exe ...

Can anyone help me with an outline of the process I should be
following?

 

[Guest]

I'm not quite sure what you're trying to do ... are you trying to call a
third party COM component from your .NET code, or trying to call a .NET
assembly from COM code?

 

[Jeff Louie]

Nick.... If you are trying to call methods in a COM dll you may be able
to use
COM Interop.

http://www.geocities.com/jeff_louie/COM_Interop/atl_com.htm

Regards,
Jeff

 

[Nick Alexander]

Hi Cam, I am trying to call a .net assembly from my .net code.

 

[Nick]

Hi Jeff, thanks for that. I think it will work, but when I tried it I
got a compiler message telling me that a dependant dll was missing; when
I looked with depend.exe, I found that a dll referred to in the 3rd
party assembly was missing. I have contacted them about this but have
received no solution as yet ...