VB6 Lovers, Unite!

By Deane Barker on March 8, 2005

Microsoft MVPs revolt: I wish them luck, but there ain’t a chance Microsoft is ever going to do anything that backs away or compromises .Net in any way.

Over 100 Microsoft MVPs (Most Valuable Professionals) have signed an online petition that demands Redmond resume development and support of “classic” Visual Basic, a-k-a VB6. […]

It’s “basically” impossible to migrate programs written in earlier versions of Visual Basic to the .NET version. […]

Microsoft’s product managers will likely say this is not the case, and will point to migration tools and strategies the company offers. But those product managers aren’t the poor bastards faced with rewriting millions of lines of source code to reinvent crucial applications, nor do the Microsofties have to swallow hard while they lose dependable business logic refined over decades.

I could see Microsoft resuming support of VB6, but development of it? No.

What Links Here


  1. I have not used VB.NET yet at all — I didn’t see the need with C#, which is awesome. I always thought the total VB.NET rewrite thing was a stupid idea to begin with. Its a totally new language from the ground up, so they should have just called it .FRED as someone once suggested.

    Crap, we’re still cranking out new/updated code in VB6 to this day. I’m not about to try and port all this code to Java or .NET, what the heck are you supposed to do?

  2. Support Classic VB!

    Yep, that’s pretty well the rallying call. And what better measure of that support than to offer it as part of the current Visual Studio product line?

  3. y hav vb6 develop more? it isn’t 2 bad, it works 4 me, well, maybe it’s bad 4 the 1s tat make complex programs. i don’t realy care, though.

  4. MAN I NEED TO REDOWNLOAD VB6….i downloaded vb6 and it got deleted off ma computer…..when i went back to da site it said microsoft wnt allow dis file download.. i need a site or somethin

    VB6 ROCKS!!!

  5. The whole thing is simple. Developers, on the benhalf of there customers have compiled thousands of lines of code, whith the knowlege that they would be supported by the software giant that is known as Microsofte (MS). Apparently MS has lost site of what matters. (The Customer) This is not about what language is the best or what programing enviroment is more productive. It is about $. It cost $ to convert code. MS has not provided a reasonable conversion model. Developers are faced with the choice. coonvert to .net or something else. Why go to .net when the company cleary is not customer focused. 5 years down the road will you need to do another exspensive rewrite? IBM was like MS is now a few year ago. they where arogent, they thought that they could do whatever they wanted and screw anyone else (it’s our company and we will run it how we want) They almost lost it and if MS is not careful they will get there as well. The customer is everything and the customer is saying they need more. They are not getting it, Plain and simple. Is VB6 Dead? Not until the customer says it’s dead. Do we need to change our vb6 code? You know we do. Do we change to .net. You would need to be a sadist if you even considerd it. Go to somthing else. Something where your sure that the parent company is customer focused and will not leave there customers high and dry. Hay MS Wake Up Its buisiness DEAL WITH IT!

  6. You know, if I were to say “VB6 rocks” in other place than this, then I would have been labelled a troll. Here’s what’s good about VB6: you can develop a GUI application quickly, hook up to databases via ODBC, rapid build cycle if you just want to hit run and see something happen. It compiles to small executables, and the DLL is included with Windows XP as standard, so you don’t have to deploy a ton of depndencies.

    I tried out Lazurus today (a freeware clone of Delphi), and found it more complicated, less intuitive, with longer compile times and bigger executables.

    People moan about VB6’s object handling, and so on, but let’s not forget that VB6 is Turing Complete.

  7. My company is currently looking for a VB6 full life cycle developer with some C++ in the Chicago area. If anyone is interested, this is a 6-12 month contract working on software for a medical device. Please give me a call if anyone is interested.

    Thanks Jake 773-824-1032 888-992-2739

  8. I’ve been developing code for about 30 years now … and VB6 is probably the most stable development platform (at least for Windows) that I’ve ever had the pleasure of working with. I was a hard-core DOS C programmer until I discovered VB3 which finally got me into doing GUI-based development. I went, of course, through VB4, VB5 then to VB6.

    On the other hand – I have been having a really difficult time embracing .Net. Yes, we do use it at the office and of the languages in .Net I still prefer to use VB.Net. Despite it’s changes from “classic” VB it’s still, IMHO, more eloquent than C# is. The IDE “creature features” certainly beat C#. Since both are CIL languages anyway I chose to stay with the BASIC syntax and take advantage of my familiarity with it.

    Though I use VB.Net at my primary job – any desktop software development I do I still do with VB6. There simply isn’t anything better in my opinion – and I’ve tinkered with a lot of different offerings. VB6/Access and/or SQL Server are a very powerful combination for just about anything in the desktop environment. As for web development? You can have it as far as I’m concerned. Sure … I’ll maintain relatively simple websites using FrontPage/ASP – but the day desktop development completely goes away is the day I’ll retire, I guess. I absolutely hate developing code to run in a browser. Yuck!

    Maybe I’m “backward” – but I still manage to make close to six figures doing back-end systems and desktop GUI development. I’ll keep VB6 until it just don’t work anymore!

    -b :-)

  9. I also have thousands of lines of code and for major projects that took me 10 years to write. I don’t think that I have the energy to write them in c#. I decided not to write any new software in vb6 because frankly Microsoft said that VB6 will be supported in Vista but who knows about later operating systems. Im writing new software in c#. I think it will be the only one left standing. When I tell my bosses that we have to re-write everything they have a dear in the headlights look and say why? You’ve been working on these programs for 10 years. Why start over? Basically I tell them that Microsoft really didn’t have a good reason for doing this and who knows where we will end up.

    I sent a letter to Microsoft asking them to put VB6 in open source. If they don’t want it then we do. Pressure Microsoft to release VB6 to open source.


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