Question on Migrating VB6 DLL to .NET

[Guest byrne1]

Here's my situation: I support and do development for a vendor supplied software package that utilizes VB6 forms and code, all of which can be customized. I have several DLL files written in VB6 that interact with the vendor's VB6 forms, etc. One of my DLLs has to be completely overhauled and I need to make the decision of whether to do it in VB6 or to do it in .NET.

 

Can someone offer up some good advice on whether I should go ahead with the rewrite in .NET or should keep it in VB6? I should mention that the vendor's code will remain in VB6 for the forseable future.

 

Althought I am perusing the net and reviewing articles and opinions on this matter, this forum has always been an excellent source for immediate professional information and advice. Thanks in advance for any advice forthcoming.

[divil]

If the rest of the product is in VB6, I'd stick with VB6 for your DLL if I were you.

[Guest byrne1]

Thanks for your response. Why do you recommend this approach? For maintainability? Seamless or streamlined interaction? Status quo?

[Thinker]

Since COM support in .Net is mostly for backwards compatibility, I

think it is safe to say that .Net DLL assemblies that act as ActiveX

DLLs are going to be slower than native ActiveX DLLs. Also, you

will have to install the complete .net framework just to use the

rewritten DLLs.