A VC 6.0 project( output is a Activex DLL) is converted to VC 2005
project and the output here is again a DLL.
When i try to include this DLL as a refernce is another VB 2005
project, i see this DLL as a COM DLL and it is creating a interop DLL
for interoperability. Why is it still seen as a COM DLL. When compiled
through Visual Studio 2005, does it not change it to a .Net DLL.
ActiveX == COM sort of. the terminology is mixed so often that the
difference between the 2 depends on when the question was asked at a
specific point in time.
If you add a COM/ActiveX reference to a .NET project, a wrapper will
automatically be created by VS *
so that you can use ActiveX objects like .NET objects.
(*) if there is a type library.
Can some one figure out what is goin wrong in this conversion.
Nothing. Your activeX project is still an activeX project.
It will still create an ActiveX component.
--
Kind regards,
Bruno van Dooren
br**********************@hotmail.com
Remove only "_nos_pam"