Question about Converting VB6 DLL to .NET

[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 software will continue to be written in VB6 for the foreseeable 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.

[Cander]

No sense in re-writting to .Net. If it works, why waste time when the rest of the app wont even be utilizing .NET? Since you would have to use COM interop to get it to work with VB6 it just becomes a COM control requireing a 21 meg set of runtimes and non of the benfits on .NET with no guarentee it will even work properly.

[hellswraith]

I should mention that the vendor software will continue to be written in VB6 for the foreseeable future.

That statement seals it for you, stay with VB6. If you were going to be migrating to .Net soon, then I would start there, but since your not, stay in VB6.