Will it still work???

[Radar]

Will my ActiveX controls & DLLs that I write in VB6 still work OK in .NET after they are compiled? Can a developer who gets one of my components now still use it later in .NET? Anyone know??

[alex_read]

Nope, they'll have to be upgraded - I've just tried inserting a standard MS one & it's not allowing me to insert it onto the form.

[substring]

From what I heard in the .NET meeting, the .NET framework does not use DLL anymore. They are doing away the registry crap, which is a big plus.

[Paul Warren]

I was on a .NET course this week and the gist of it is :

we'll no longer using COM objects ( ActiveX stuff )

.NET uses libraries called assemblies which are like COM objects except that they carry all the information that was in the registry around with them. You can just drag and drop them into directories and they work, no need to register them. Other differences are that they are not in binary, they're in something called Intermediate Language ( IL ). It's a big subject but you should still be able to use you're COM abojects because .NET will put a wrapper around them so they can communicate. When you want to add a component/reference select the COM tab and choose it from there, don't just browse and select it.

Like I said it's a huge subject but if you've got any more questions just post them here.

[spike232]

i have only found one problem so far with it wrapping the coms, the microsoft messenger ones worked except for the events, if u tried to access the events it crashed, i had to make a vb6 dll to access it then wrap the vb6 to .net to use it, but it works