Still using VB 6?
Many users remained in VB6 because of the complexities of data bindings in WinForms in .NET 1.1. .NET 1.1 data bindings made the complex stuff easy, but often made the easy stuff complex. This was a major source of frustration, but most especially to VB developers as things that were easy in VB 6 were not so easy in VB.NET, even though VB.NET was much more powerful. This prompted many VB users who created mostly client server applications (which is the majority of VB developers) to remain in VB6. In .NET 2.0 (VS.NET 2005) the data bindings have been completely rethought and now not only are the complex things easy, but the easy things are easy again as well. If you remained in VB6 because of this, now is the time to look at .NET again and move to VB.NET. VB.NET and VB however only share the name, and a similar syntax. .NET enforces “best programming practices” and this has forced VB as a language to evolve. However two new resources have been posted online to assist VB6 developers in this migration path:
- MSDN: Upgrading Visual Basic 6.0 Applications to Visual Basic .NET and Visual Basic 2005
- gotdotnet: patterns & practices - VB6 to VB.NET Migration Guide
Comments
Anonymous
November 19, 2006
I'm still using the vb 6. I prefer to learn PHP insted vb .net It was the best programer language for me i learn a lot of things to do in vb6 and I help to continue with a better version with the same code, but who nows?Anonymous
September 06, 2007
I was hesitant to migrate from VB6 also, but made the move after several years waiting on the sideline. .NET is the way to go moving forward. Migrating VB6 codes to .NET is not easy. You will have to consider the cost and benefits for the projects.