When They Rip It from My Cold, Dead Fingers
When Should Visual Basic 6.0 Be Killed?
Visual Basic 6 is going to be around for quite a while. VB .NET is, however, taking over and the reasons for upgrading are becoming more compelling with each new version. With the release of 2005, many of the remaining issues about upgrading are going to be addressed, includes edit & continue.
While VB 6 may be around for a long time, it can already be seen that employers looking for VB experience are looking for .NET people more so than those without. For those doing professional development, the need for VB 6 in new development should be going away sooner rather than later. As .NET becomes a standard within Windows systems, so will development using .NET.
Although there are a number of reasons to stick with VB 6, Microsoft is working to tilt the scale to VB .NET. Microsoft made a tough decision to avoid hurting VB .NET with backward compatibility. Statistics are already starting to show that .NET development is becoming more predominant.
The promise of using VB .NET is the ability to tap into the full .NET Framework and to make Visual Basic a first class programming language. As Craig Symonds stated, "[VB .NET] removes the glass ceiling in 6.0."
If you are a professional developer doing VB 6.0 development, the days of developing new systems with your tool ofchoice are numbered. It may be time to start looking at VB .NET even if you have to do it on your own. Otherwise, you may be working with the guys who didn't want to upgrade from VB 3.
After all, Visual Basic 3 could do almost everything in its day, too!
Developer.com, CodeGuru, and DevX are just a few sites that have numerous articles on Visual Basic .NET. Additionally, VBForums, CodeGuru.com, and DevX offer discussions on Visual Basic .Net. For code samples, you can check out FreeVBCode and CodeGuru. Microsoft also offers numerous Webcasts and chats on VB .NET.
# # #