How do I debug a Web project with VS2005 in Vista IIS 7?

Debugging the WEB project core with vs2005 in Vista IIS 7 addresses the following issues:
Vista itself has the necessary IIS7 components for Security user Account Control (UAC) installation. Vista's IIS7 and IIS 6 have changed at the bottom, how we let IIS7 run in a compatible IIS6 way. Because VS2005 does not support IIS7.
The screenshot below shows how to configure these points to ensure that VS2005 can debug the IIS based Web project in the Vista operating system.

First, install the necessary IIS7 components

IIS7 is broken into a number of components that are not installed by default and you need to install these components.

The following figure corresponds to the function, which can be opened by:
Start--> Control Panel--> program--> turn Windows features on or off



1, VS2005 does not recognize IIS7, to let it identify IIS7, you need to install a IIS7 plug-in: IIS6 management compatibility;

2. IIS default security: In VS2005, if you want to debug a site, you must have integrated Windows authentication

The other two, in some cases, can also be used:

Digest authentication uses a Windows domain controller to authenticate users who request access to content on the WEB server.

Basic authentication requires a user to provide a valid username and password to access content.

3, to debug asp.net of course to install the IIS support asp.net components.


Second, configure IIS7

1, IIS7 After installing the above components, some features are not enabled, you need to enable it:

The following configuration features you can

Control Panel--> Management tools-->internet Information Services (IIS) Manager program

After you open Internet Information Services (IIS) Manager, in the lower part of the middle section, you can see the authentication configuration entry, which is the following interface:



Just a few of our additional authentication needs to be enabled on the site you want to debug.

Note: It is the site you want to debug, not the application directory you want to debug.

2, the IIS7 application pool settings

The IIS application pool is divided into two types based on the managed piping pattern: integration and Classic

In integrated. NET mode, applications should not specify ASP.net module components in the <system.web>/
The classic. NET pattern is the way we used to be in IIS 6 without the above restrictions.

After all, now that Longhorn Server is far away from us, we certainly want to be compatible with the IIS6 mode of window 2003, so we need to modify the site's application pool settings, as shown below:



My screenshot above is to use the existing Classic mode of the application pool, you can also build a classic model of the application pool, and then use the map to configure the corresponding site to use this classic mode of application pool.


Third, the start of the VS2005.

Because of Vista User Account Control (UAC), we should run Vista as an administrator in order to avoid the problem of not having permissions in debugging. The following figure:



Resources:

enabling ASP.net 2.0 debugging on Visual Studio, IIS 7.0 and Vista
Http://www.thousandtyone.com/blog/EnablingASPNET20DebuggingOnVisualStudio2005IIS70AndVista.aspx

Tips and tricks: using Vista IIS7 in VS 2005
Http://weblogs.asp.net/scottgu/archive/2006/09/19/Tip_2F00_Trick_3A00_-Using-IIS7-on-Vista-with-VS-2005.aspx
Http://blog.joycode.com/scottgu/archive/2006/09/20/83906.aspx

Running Web applications on Windows Vista with Visual Studio 2005
http://msdn2.microsoft.com/en-US/library/aa964620 (vs.80). aspx