More on VB6 Support


There have been a lot of questions raised about the “end” of support for Visual Basic 6.0 recently that are worthwhile addressing.  Let’s just get the biggest question out of the way: Support is not ending.  Let me say that again: Support is not ending.

 

So what happens on April 1st of this year?  The change in support that we announced back in 2002 is that we transition from a warranty support model to a paid support model.

 

The thing that is really affected by this is the 2 warranty incidents that came with the Visual Basic 6.0 box. If you’re an MSDN subscriber, you have the 2 or 4 support incidents that you received along with your subscription.  Those will still work during the extended support cycle.  If you need to purchase support you can buy a single-instance support question for $245 or a package of 5 incidents for $1225.  You can also buy a web-only incident for $99.

 

Microsoft will continue to provide security fixes free of charge to the VB6 runtime through the extended support lifecycle.  The VB6 runtime shipped as a part of Windows XP and so will continue to be supported throughout Windows XP’s support timeframe.   The real question being raised is around free warranty support for developing applications with Visual Basic 6.  You will continue to have access to all security fixes and self-help online support options (including knowledge base articles, online product information etc.).

 

 

The VB6 lifecycle page at http://msdn.microsoft.com/vbasic/support/vb6.asp contains some more information.

 

Rob Copeland, the Product Unit Manager of the VB team, wrote about this in his first blog post.

 


Comments (9)

  1. Frustrated Customer says:

    Who cares about the ability to call MS for free. Who calls MS anyway? What just kills me is the fact that SP6 is crap. It’s almost like bugs were added on purpose to help kill VB.

    I know it sounds far fetched but look at the facts. There are VB3/4/5 KB articles that have their URLs set in stone. VB6 KB article URLs change contantly. Don’t want anyone to find them?

    VB3/4/5 sample code is still in place. VB6 code moves from page to page and finally you get a "sorry, this page has been removed" message.

    So, the problem is NOT that we can’t call MS for free. It’s that MS is doing everything it can to kill VB6 and shove .Net (bloatware) down everyones throat.

    Ending support is different than purposely killing a product. Who cares about MSs attempts to help VB6 devs "migrate" to dotnet. Most VB6 devs I know, that haven’t migrated, aren’t going to at all. If/When they do change languages, the stats show that upto 50+% of them will be leaving MS dev tools behind all together. More are switching to C# because they believe MS won’t break that (lots of luck)