Hi all

With Visual Studio 2005 on Vista using IIS7 you had to make all kinds of adjustments to enable ASP.NET debugging. You had to install some extra IIS features, change the authentication and application pool settings, run VS as administrator, ... I think this blog post by Mike Volodarsky was very popular those days:

Now I would like to know what changed since Visual Studio 2008 has been released. Has it become easier to debug ASP.NET applications or not? Which features and configurations are still required? Is there any difference between a 2.0 or 3.5 ASP.NET applications.

Hope someone can clear things up.

I've been working with VS2005 on IIS7 / Vista since June. 3 weeks ago I uninstalled VS2005 and installed VS2008. It works great - I haven't had one problem. I kept the settings in IIS7. I'm pretty sure it works out-of-the-box...

It might be just force of habit, i usually use "Control Alt P" to attach to the w3p.exe process and that works like a charm in VS2008 on Vista/IIS7

Why should that be nessecary?

F5 works brilliantly for me...

 As i stated, it's just force of habit....  and just wanted to point out that this method works out-of-box... nothing more

 

I asked because I want to perform a clean install on my computer with only VS2008 installed (no longer VS2005). I was hoping the IIS installation and configuration would be easier in combination with VS2008.

Nobody any experience with this? 

 To the original question of:

"Has it become easier to debug ASP.NET applications or not?"

 Yes... RTM of VS2008 has fixed the issues/needed workarounds