What they aren’t telling you about VB6 support
Sun, Mar 13 2005 16:41
This last couple of days there’s been some posts by Microsoft people trying to re-assure folks that VB6 support is going to continue for some period of time. But what they aren’t telling you is …
As some of you may know, VB6 is at SP6. That’s frozen now for time infinite despite the known problems with SP6. And yes SP6 did bring about new bugs, so installing SP6 on a system can break a happily working SP5 app.
In fact a lot of people have been deliberately staying away from SP6 because of it. Only last month or so Microsoft released an update to it’s AntiSpyware software which is written in VB6 of course. The question is which runtime did they distribute, SP5 or SP6 ?? A: SP5. Yep they don’t even trust their own last SP.
So now as Microsoft walks away from providing free service packs, and leaves us with the last set of introduced bugs, you now have to rely on all vendors to play nice with each other, and hope that Microsoft doesn’t release updates for the common components Office uses or for XP. If they do, you will need to keep different build versions for all your development to ensure they work.
Note: you are not licensed to distribute those components that ship with Office or XP.
That is, the ability to simply specify the latest service pack, and point someone to a web site is now gone.
What still exists of course is phone support (for a fee) which I’ve never had to use, and hot fixes (for a fee) which thankfully I haven’t had to use yet. As SP6 isn’t going to be fixed, and considering Office and XP will still do their own thing there, then I expect this is one that may need to be used in the not too distant future