VB 6 to VB.Net versus VB 6 to C#

The "mechanics" of the conversion are the same whichever language you choose: .NET controls are different from VB6 controls, so it is unlikely that you can keep much (if any) of your current UI code base without massive amounts of testing and probably headaches.

Having said that, there are automated conversion tools which will convert the code to VB or C# for you - a very quick google found this: VBUC[^] though I haven't used it myself.

Personally, I would probably hand re-develop it in C# if only because it removes the temptation to use "old" and incompatible VB6 coding methods with VB.NET - if you have to do it in C# then you will end up with a C# solution. If you go VB6 to VB, then you could easily end up with a "mashup" that suits neither language.

Depends on you though: How familiar are you with C#?

Let me start by saying I'm an out-and-out C sharp programmer, and I love the language. I've done some VB6 so I at least am familiar with the world you're coming from. So, it would be tempting to say "go C sharp." But I also have a friend I respect who swears by VB.

Realistically, there are more serious considerations - such as the timeframe you have for making the conversion, your own goals regarding learnign a new programming language, whether you are the sole developer of the application, and if you are or will be part of a team, what is the language the team has the most experience with.

Both languages will cope with the UI elements you have to use; if you use a third-party set of UI controls you might take a look and see if they support both VB.Net and C sharp (I see no reason why not since a control is just code in a .Net assembly - and that can be referenced equally by both languages). Similarly, both languages use the same .Net framework, so they both have the same access to SQL database as each other. And, using those framework elements, whether from VB.Net or C sharp, will be an identical learning curve.

I'd say you are probably better off moving to VB.Net because on that path you only have to learn the delta between VB6 and VB.Net, not the whole of a new language.

You should take a look at http://www.red-gate.com/products/dotnet-development/reflector/[^] and look at how it can disassemble a .Net assembly into any of several .Net languages. You should also google tools that might help with your conversion. The availability of a suitable tool might help influence your decision.