VB6 to VB.net, OCX to ActiveX

[Romain TAILLANDIER]

Hi Group

I had a small SDK projet in VB6. It allow me to use an OCX.

I have open it with VS.net, and the project have been traduice to VB.net.
The OCX have been traduice to 2 DLL.
Is that 2 dll are an ActiveX ?
Are they could have been altered by the translation ? (is it correct english
??)

It seems that the dll works fine but how can i verify it ?
I try to use the Depency Walker (depends.exe) to read the DLL entry, and it
doesn't work. that makes me think that they are altered.
how do you think about that ?

thanks
ROM

 

[Scott M.]

..ocx and ActiveX are the same thing. .NET does support interoperability
with COM based components, but if you are saying that you opened your VB 6
project in VB.NET and the code was migrated, then you are no longer using
ActiveX (.NET does not create ActiveX ...or any COM components for that
matter).

If you did migrate your code, you now have a .NET Managed Assembly (.dll).

 

[Romain TAILLANDIER]

Thank you Scott !!.

I have effectively migrate my code (from VB6 to .NET)
and i understand that i have now a .NET Managed Assembly (.dll)

where can i found a good and simple explain of what are OCX, ActiveX and
..net Managed Assembly ??? (thinking that i am a beinner with those concept)

My OCX have been migrate to 2 DLL. I join both in the references of my C#
project, and it seems to work fine. But how can I make sure that the OCX
fonctionalities have not been altered during the migration, in the
resulting DLL ?

Thanks
ROM