Friday, September 29, 2006 6:37 PM
codingsanity
No Vista for me
I just cannot stress how upset I am with the Visual Studio team. Since VS2005 was released, developers have been begging Microsoft for a service pack, or even to make the hot fixes freely available. No such luck. Anyway, about 11 months ago, a guy called Scott Wiltamuth announced that the Service Pack would be released in the first half of 2006. Well, since then it's been a bit of a black hole for this alleged service pack. As the bug reports have piled up and up and up, the VS team has been as quiet as a mouse on information about any fixes. We got all sorts of information about new cool things coming down the pipeline, but nothing on the fixes to the last cool things that came down.
Yesterday, in the dying days of Q3, Somasegar announced... wait for it... the BETA of the service pack. So, not in the first half of 2006, but more like 2007. But of course, the VS team must have had some good news for all the .NET developers out there, right? Yes indeedy, Visual Basic 6 will be supported in Vista!
*crickets chirping*
Ummm, that's great Somasegar, but how about those development tools for that managed framework you spent years convincing us was such a good idea? Umm, well, there's good news and bad news. The good news is that VS 2005 SP1 will run on Vista, but will have compatibility issues.
Really?!? You've hugely overshot a delivery date for a desperately needed service pack, and you can have the audacity to say it'll still have compatibility issues with the new flagship OS?!? Well, just for some more good news, VS 2003 and 2002 will not be supported on Vista, in flagrant violation of Microsoft's own support policies. Interesting, VB6 - not supported by MS - will work on Vista. VS2003 - still fully supported by MS - will not work on Vista. Apparently the reason has to do with the debuggers, they basically need a lot of work on them to make them Vista-compatible. Microsoft couldn't be bothered to do this work on the older releases of Visual Studio. This is quite simply unacceptable, VS2002 & 2003 are still in mainstream support and will be for years to come, yet that mainstream support does not extend to the new mainstream OS! What this decision means is that Microsoft have lied about their support policies. If we cannot trust that, how are we to make meaningful purchases of Microsoft products? Am I supposed to introduce a fudge factor into support durations?
"Yes I know that this $1,000,000 purchase SAYS it'll be supported for ten years, but in reality it's ten years or new OS, whichever comes first". I can see the finance director being very impressed by that.
What most irritates me about this is that I won't get to run Vista on my development machine. I've played around with Vista and really like it. but I write code that has to run on all .Net Framework versions, and so one of my dev platforms is VS 2002, so until Vista supports that or until .NET 1.0 and 1.1 are no longer installed anywhere on Earth, I cannot drop them. It's a little thing called backwards compatibility, and it's a very sad day when I have to suggest that Microsoft check out what that means.
I'd like to leave you with a quote from a guy called Halo_Four:
"Microsoft products, which I generally prefer, are popular for two reasons: general support for a wide array of current and legacy software, and wide support for the development community. In one fell swoop Microsoft is proposing to stop both. This is a lose/lose situation for all of those who are involved."
Filed under: Tools, General, Community