3 ms·

At this point, I don't know why MS bothers to keep VB .NET going. The languages are effectively the same. AFAIK, you can map class-by-class, method-by-method fr

by angdis 16y ago

At this point, I don't know why MS bothers to keep VB .NET going. The languages are effectively the same. AFAIK, you can map class-by-class, method-by-method from one to the other. How hard would it be for VB .NET programmers to migrate over to c#? My guess is that it would be FAR EASIER than the transition they took from VB6 to VB .NET 2003.

GFischer 16y ago
Here at the large insurance company I work for, we have a LOT of Visual Basic 6 code. And, the natural migration path has been to Visual Basic .NET (we have quite a lot of it as well). Our parent company has multimillion-LOC VB6 programs, which they are migrating to Visual Basic .NET As long as huge companies such as those continue pushing for VB.NET, Microsoft should be wise to support it. It's not that I would mind moving to C# (it would take me out of my comfort zone, but it wouldn't be so bad), but what about all that code?