In Vista IIS 7, using vs2005 to debug a web project, the following problems are to be solved:
1. Vista’s own User Account Control (UAC) in terms of security
2. Install the necessary IIS7 components.
3. Vista’s own IIS7 and IIS 6 have changed at the bottom. How do we make IIS7 run in an IIS6-compatible way? Because VS2005 does not support IIS7.
The following is a screenshot to illustrate how to configure the above points to ensure that VS2005 can debug IIS-based web projects in the Vista operating system.
1. Install the required IIS7 components
IIS7 is divided into many components, and it is not installed by default. You need to install these components.
The corresponding functions of the figure below can be opened through the following steps:
Start --> Control Panel --> Programs --> Turn Windows features on or off
1. VS2005 cannot recognize IIS7. To make it recognize IIS7, you need to install a plug-in for IIS7: IIS6 management compatibility;
2. IIS default security: In VS2005, if you want to debug the site, you must have "Integrated Windows Authentication"
The other two can also be used in some cases:
Digest authentication is the use of a Windows domain controller to authenticate users requesting access to content on a Web server.
Basic authentication requires a user to provide a valid username and password to access content.
3. To debug ASP.net, of course, IIS components that support ASP.net are installed.
2. Configure IIS7
1. After IIS7 has installed the above components, some functions are not enabled, you need to enable them:
You can use the following configuration functions in
Control Panel --> Administrative Tools --> Internet Information Services (IIS) Manager program found
After opening the Internet Information Services (IIS) manager, you can see the authentication configuration item in the lower part of the middle part. Double-click it to be the following interface:
The several authentications we just added need 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. Settings of IIS7 application pool
IIS's application pool is divided into two types according to the managed pipeline pattern: Integration and Classic
In integrated .NET mode, the application should not specify the ASP.NET module components in the <system.web>/<httpModules> configuration section, but should use the <system.webServer>/<modules> configuration section to load the ASP.NET module components.
The classic .NET mode is the way we used to IIS 6, without the above limitations.
After all, Longhorn Server is still far from us. Of course, we need to be compatible with the IIS6 mode of Window 2003, so we need to modify the application pool settings of the site, as shown in the figure below:
The screenshot above is a use of the existing classic mode application pool. You can also create a classic mode application pool yourself, and then use the above image to configure the classic mode application pool used by the corresponding site.