VB to C#
-
VB 6.0 or VB.NET? - Nick Parker
My Blog | My Articles -
Try this: http://www.kamalpatel.net/ConvertCSharp2VB.aspx[^] It was the first result in a Google[^] search :) --- Dave
-
npqk wrote: VB to VB.Net Just open your VB6 project in VB.NET. Yes, even I am blogging now!
-
If you're talking about VB6 or older (it uses a completely different runtime and relies on COM - not the .NET base class library and third-party assemblies), then a better question to ask yourself is "Why should I convert?" If you're doing it just to jump on the .NET bandwagon you're doing it for the wrong reasons. You need trained staff to maintain the code and build upon it. Just converting the code doesn't gain you much (besides a 20+ MB runtime that now has to be installed on your clients' machines before your application can even run). There's a lot more power wrapped up in the .NET Framework and more efficient code and better application designs can be written using .NET. Just converting your VB6 code will end up using a lot of inefficient code accessing COM objects (and you'll take a marshaling performance penalty more so than with VB6) for which there's probably replacements for in the .NET BCL and third-party libraries (no marshaling, just direct access). There's a lot of other reasons besides those I've listed above. Googling for such topics I'm sure will uncover more reasons. This posting is provided "AS IS" with no warranties, and confers no rights. Software Design Engineer Developer Division Sustained Engineering Microsoft [My Articles] [My Blog]