VB6 Developer Struggles

By Deane Barker on April 20, 2006

Is There A Future for VB6 Developers After .NET ?: Interesting post and conversation coming from a “24-year VB programmer” struggling with the forced upgrade path to VB.Net.

If I could simply whizz through coding with VB6, I found myself stumbling like an infant child with VB.NET plus the lack of many useful and already mature features which was available in VB6.

Responses like these are common:

That was a long question for such a short answer: No.


They’ve abandoned you, and *ed you over. There really isn’t any other way to look at it.

Over a year ago, we posted on a semi-organized protest over the forced upgrade to .Net. The petition is still going strong.

What This Links To


  1. And I thought I had it bad when ‘printf’ and ‘scanf’ were replaced by ‘cout’ and ‘cin’…

  2. Oh hey, this is like the train ticket salesmen whose overweight truck stalls complaining that the 3:50 smooshed his vehicle! Hellooooo, you should have seen this train coming down the tracks. If you couldn’t save your truck than you could have at least jumped to your own physical safety.

    Sorry, but I’ve got little sympathy for this type of kvetching. I remember when 4.0 came out, oh my goodness, the whining and moaning about object-based programming. Then 6.0 came out and every access hacker thought he/she was going to die.

    When .NET 1.0 and everyone should have seen the handwriting on the wall. .NET 2.0 took how many years to develop? And during that time how many articles and discussions were raised regarding the “JAVA-ification” of VB?

    C’mon kiddies, it’s called a career and you’re responsible (not you Deane) for keeping up with trends in technologies, languages, systems, etc … Seriously, over the past couple of years, had the author of the article taken time to learn how to dig into the feature rich class libraries he would have known how to make that 3 month .NET test project in the same time as its 1 week VB6 counterpart.

    Computer languages and compilers change all the time. Otherwise, I would have stuck with Borland’s Turbo C 2.5 … which to me was the perfect junction of utility and simplicity.

  3. I did experiment with VB.NET and I found out it took me “years” to actually do a “simple” program to connect to a database and display reports.

    That statement explains a lot.

Comments are closed. If you have something you really want to say, tweet @gadgetopia.