VB 6.0 Support Clarification
Two points from my previous blog that I was not totally clear on in my previous post so I wanted to highlight them.
First, during the Extended support period (April 1st on) if you have an MSDN subscriber or have a Premier or Alliance support contract the included free incidents do not expire and are valid through the extended support period. I was a bit to vague and implied to some that these incidents would also expire. This is not the case.
Second point of clarification for those of you with production code. The VBRuntime ships in the box with Windows XP. This means that the VBRuntime will continue in the Maintream support for 2 years for when ever Longhorn ships and 5 years after that point for Extended Support (7 Years total from the shipping of Longhorn which won't be tomorrow). When we talk about the end of Mainstream support for Visual Basic we are talking about the development environment. Since the runtime is part of Windows XP you have some time until this support stops.
So problems with your production applications will be supported for some time to come. Problems with the development tool itself will continue for another 3 years.
Just so I don't start some other rumor, the VBRuntime ships with XP, this does not mean it won't work with Longhorn. I have checked with the Development group and it will work with Longhorn. See my comments in the VB 6.0 Support blog for more details.
I hope that clears things up a bit for more people. Sorry for any confusion.
Comments
- Anonymous
March 12, 2005
For what it's worth...
http://classicvb.org/ - Anonymous
March 13, 2005
NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO - Anonymous
March 14, 2005
we5afg55 - Anonymous
March 14, 2005
ghljklo - Anonymous
March 14, 2005
1 - Anonymous
March 14, 2005
425-0052536 - Anonymous
March 14, 2005
The comment has been removed - Anonymous
March 15, 2005
I program since a long time with VB and some time ago with Access. What is now happen with VB we see before with MS Access for example. From Access 2.0 till today the things change very much and almost all the time you've to adapt much in your code.
For now, Microsoft promise the best for .NET ... but what is in 5-6 years? Perhaps then we move to something again better and must adapt again all the things?
Perhaps is time that Microsoft realize that peoples cannot rewrite every 5-6 years their applications. Why not update the VB6 to a VB7 with new features? - Anonymous
March 15, 2005
My opinion is:
1. For web development, consider other platforms/languages such as Java, PHP, ...
2. For desktop development, consider cross-platform tools such as QT, Java, ...
OSS - Anonymous
March 15, 2005
The comment has been removed - Anonymous
March 15, 2005
The comment has been removed - Anonymous
March 16, 2005
I know what you mean about the upgrade wizard. I Tried to run a couple of my applications thru the wizard. After it was done I had so many fixes to do, I decided I would have to completely rewrite the app from scratch. I've been trying to learn the vb.net but is slowly progressing as I still need to work on my VB6 applications. I can't migrate to vb.net my VB6 app's because the Development does not run on Win 98. I can't upgrade to Winxp, because it does not support the DOS software I have to use at work. A lot of catch 22. I work for a County Government and they won't get me a better laptop to use. Budgets!!! - Anonymous
March 16, 2005
The comment has been removed - Anonymous
March 16, 2005
The comment has been removed - Anonymous
March 17, 2005
aa - Anonymous
March 17, 2005
hello - Anonymous
March 17, 2005
aabbebrnnrrrr - Anonymous
March 31, 2005
i want to know which all platforms suport vb - Anonymous
March 31, 2005
which all extensions are for vb forms in linux - Anonymous
March 31, 2005
tgs` - Anonymous
March 31, 2005
i need it for brainbench study and like the book so much and it is interesting.