Lazycoder

VB 6 is dead, long live VB6

Randomize – VB6 Hold-Outs Grab Pitchforks and Torches

I’m with Richard and others on this one. Just because VB6 != VB.NET doesn’t mean that VB.NET should provide backwards compatibility. It’s not like Microsoft didn’t TELL you about this. It’s not like at PDC 2000 they didn’t say “VB.NET is not compatilble with VB6″. That was FIVE YEARS AGO PEOPLE. You are just NOW getting around to “protesting” VB.NET and the abandonment of VB6? I was doing primarily VB6 development at that time and I remember sitting in the sessions at PDC 2000 thinking, “Man, I can’t wait to dump VB6 and re-write my stuff in VB.NET and C#”. Hell, the VB6 people should be ECSTATIC that MS isn’t going to be updating their environment. Visual Studio 6 is more stable that Visual Studio.NET 200x. Some people prefer using Visual C++ 6.0 over Visual Studio C++.NET (or whatever it’s called).

So while I’m sympathetic, I’m not THAT sympathetic. There was less complaining when Java went from version 1.2 to version 1.3 and half the GUI code broke as a result. Just hike up your pretty pink pinafores and migrate your code to VB.NET. Those of us that might have to maintain your VB6 code at some point will be eternally grateful.