Is VB migration scary?
Have you made the VB migration or do you still have tons of VB6 code running in your organization? I'm always surprised in our consulting and debugging work how much VB6 code is running. I'm a strong advocate of not breaking working code, but since Microsoft ended all support for VB6, one should have already started planning what you're going to do with that code.
Some say a VB migration is too big. I would argue that VB6 had limitations that VB.Net has removed. I do not think that the time spent learning VB.Net is so overwhelming that the change is difficult to justify.
It is hard for me to speak to how difficult the transition was from VB6 to VB.Net. I started working with VB.Net when Visual Studio.Net was in the alpha release. While the syntax of VB6 is drastically different from VB.Net, which I imagine could intimidate people who don't feel a need to move onto a new platform, I think that the amount of time I spent learning VB.Net was quickly made up for in increased productivity when building ASP.Net pages versus ASP 4.0.
I would contend that VB6 had limitations that VB.Net has removed. I do not think that the time spent learning VB.Net is so disturbing that the change is difficult to justify.
VB6 existed for one reason and one reason only -- to hide the complexities of COM.
VB6 was the Matrix, while VB.NET is as powerful as C#. Some folks say, why do the VB migration? I'll just move over to a language with "C" in it, and maybe I'll get more money? VB.NET aims to hide nothing -- and the exposure is scary to many.
Want to learn more about the importance of a VB migration? Please
Read my blog at http://www.migrateto.net/blog/vb-migr...