Old component usability in .NET

[OpticTygre]

Hey folks,

I have a component that I know was written in VC++ 6.0, and worked great
within Visual Studio 6. In .NET, I'm able to use it as a reference, check
out all the properties in the object browser, and even have it accessible
via intellisense in my VB.NET code. All this, but I don't know if it's
possible to actually use it's functions properly. Are the events and
methods of objects built in older versions of visual studio still accessible
through .NET, even though they don't use the CLR? From what I've seen they
aren't, but I may be doing something totally wrong.

-Jason

[Samuel L Matzen]

OpticTygre,

If you have gotten to the place that the COM object displays in the object
browser then you have a valid reference to the COM object and VisualStudio
has implemented the necessary interop layer so you can communicate with the
COM object.

To answer your question directly: Yes, you should be able to use the COM
object in your VB.NET programs. Actually much of the .NET framework
interacts with COM objects.

-Sam Matzen
"OpticTygre" <op********@adelphia.net> wrote in message
news:Hv********************@adelphia.com...

Hey folks,

I have a component that I know was written in VC++ 6.0, and worked great
within Visual Studio 6. In .NET, I'm able to use it as a reference, check
out all the properties in the object browser, and even have it accessible
via intellisense in my VB.NET code. All this, but I don't know if it's
possible to actually use it's functions properly. Are the events and
methods of objects built in older versions of visual studio still accessible through .NET, even though they don't use the CLR? From what I've seen they aren't, but I may be doing something totally wrong.

-Jason