I hate chiming in on topics that have already run rampant throughout the dev blogosphere, but I feel like I need to because people are being so negative about the lack of support for Visual Studio (VS) on Vista.
First, let me explain the situation for those that don't know. Apparently, Microsoft's past 3 development environments are being considered "incompatible" with Windows Vista. That's a pretty simplistic answer, which is exactly why there's been so much hubub in the dev community. Obviously, developers are among the top Vista pre-release users, so this would obviously be a concern. The problem is, people aren't seeing the big picture, what the real problem is, and what this really means.
The real problem lies within the fact that some of the advanced features, like advanced debugging, are the ones that are causing the problems. These problems are directly related to the new security features in Vista, which change the way memory is managed, for instance. Just like I said when Symantec was griping about Vista's security features locking out competitors , the very same features are also causing compatibility issues with Microsoft's own software. I knew this would come up eventually, it was just a matter of what product and when. Hopefully, this will help arm the battle against those who would rather loosen security to fatten wallets .
Since I've been on Vista, I've done all my dev work in Virtual PC, so this hasn't affected me. Although, given the features that are problematic, I don't think it would affect me that much. There are plans for a service pack of some sort (after VS 2005 SP1) that will be specific to Vista and hopefully fix all of the issues there are with VS -- at least, the latest release. There are no plans to update VS 2003 -- as there shouldn't be, in my opinion.
One thing that everyone needs to realize is that Vista and Visual Studio are two very big products. If Microsoft is going to commit to supporting different release combinations, they have to be able to do so 100%. There is a ton of money that goes into supporting these products and it just doesn't make sense from a financial standpoint to support something that you know will be problematic. There's a work-around and it's actually a nice one, in my opinion. Only the official release will truly show us how this will affect everyone on the larger scale, tho.