Should a VB6 shop start using VB.NET, or should they switch to C#?
In addition to my business, I work for a county-level government agency in Florida. Our legacy system is a 1.2-million-line steaming pile of VB6. While it works (for limited definitions of “works”), there’s no way we’re going to be able to maintain it forever, and we’re certainly not going to write new projects in VB6.
Since we’re a Microsoft shop, we’re going to the .NET platform. The choice, however, is whether to use the familiar syntax and stick with VB.NET, or to harness the additional power of C#. I favor the latter approach, and I’m pleased that the Powers That Be agree.
The world of .NET development is dramatically different from VB6. Techniques that work in VB6 no longer work in .NET; techniques that work in .NET fail miserably in VB6, and even some things that work in both environments are sufficiently different to be difficult to understand.
Using similar syntax to express dissimilar ideas is a recipe for confusion.
Appreciate it for all your efforts that you have put in this. very interesting information. “A sense of humor is the ability to understand a joke and that the joke is oneself.” by Clifton Paul Fadiman.