Join the Windows XP club... for 5 more years or so
If you’re a developer today writing .NET apps, you’re either writing them with Visual Studio 2003 or 2005. I don’t know what the actual numbers are out there, but for those writing apps with VS2003, forget about developing on Windows Vista when it ships. You won’t be able to run your precious IDE. Visual Studio 2003 is not supported on Vista. Does it mean it wont run? Maybe, I’m not sure, but the “official” word (and what’s flying around the blog-o-sphere these days) is that it won’t be supported. Also if you’re running VS2005, you’ll need to install SP1 (which just went public recently).
To me this means I’ll be running Windows XP for another 5 years until the next OS comes along. It works, the kinks are pretty much out of it now, all my hardware works with it, and I can develop apps using VS2005 and 2003 along with .NET 3.0 (God, I still hate that name) on it. I’m sure MS will at least consider correcting this (especially since almost every feed I read is discussing this problem). I mean, how freakin’ hard is it to support 2003 on the Vista Platform? Don’t answer that, and I swear I’ll ostracise the next blogger who uses “first-class” with anything and Microsoft, that saying is getting so overused.
Is Visual Studio 2003 really that “legacy”?
What really kills me about all this, is that your good old VB6 IDE will run fine and be supported. VB6! I thought we killed that thing off when we had the chance. While I understand Microsoft is focusing their efforts on supporting VS2005, I would think you generally have a few good brain cells to know that most people haven’t switched over/upgraded yet and it’s not going to happen overnight for some (most?) apps. So why wouldn’t you support the masses?
Or am I that out of tune with the universe and everyone has silently moved to VS2005 and this isn’t an issue.
If that’s the case, why is everyone blogging about this?