Found on LonghornBlog this interesting postfrom Robert McLaws

{

Last night I posted about Visual Studio Support on Windows Vista. Scott Guthrie, GPM from the Developer Division, had this to say on a blog this morning:

The big technical challenge is with enabling scenarios like advanced debugging. Debuggers are incredibly invasive in a process, and so changes in how an OS handles memory layout can have big impacts on it. Vista did a lot of work in this release to tighten security and lock down process/memory usage - which is what is affecting both the VS debugger, as well as every other debugger out there. Since the VS debugger is particularly rich (multi-language, managed/native interop, COM + Jscript integration, etc) - it will need additional work to fully support all scenarios on Vista. That is also the reason we are releasing a special servicing release after VS 2005 SP1 specific to Vista - to make sure everything (and especially debugging and profiling) work in all scenarios. It is actually several man-months of work (we've had a team working on this for quite awhile). Note that the .NET 1.1 (and ASP.NET 1.1) is fully supported at runtime on Vista. VS 2003 will mostly work on Vista. What we are saying, though, is that there will be some scenarios where VS 2003 doesn't work (or work well) on Vista - hence the reason it isn't a supported scenario. Instead, we recommend using a VPC/VM image for VS 2003 development to ensure 100% compat. Hope this helps - even if the answer isn't entirely what we'd all like it to be, Scott.

So all the developers out there need to take a deep breath and chill out. Microsoft isn't trying to screw you. The Windows platform changed on so many levels that the advanced capabilities of the VS debugger are difficult to support, especially under UAC. That's why a fix is going to have to be put out for VS2005. VS2003/2002 will still run, it just won't be supported. Look, a lot of companies are going to have to put out service packs for their apps to improve compatibility with Vista. Did you honestly think Vistal Studio was going to be any different?

}