The article "Improving the stability of ASP.NET applications through system configuration" talks about the configuration method under Windows 2000 (essentially under IIS5.0, XP professional is also the same as 2000). Today we will take a look at Windows 2003 ( Configuration method under IIS6.0).
The default running mode of IIS6.0 is process isolation mode, which supports multiple ASP.NET service processes to run in parallel through the application pool. Most of the <processModel...> section in the machine.config file mentioned above Settings are ignored in this running mode, including the three properties we mentioned earlier. But don't worry, the configuration under IIS6.0 is simpler and more intuitive. The specific steps are as follows:
1. Open "IIS Manager"
2. Find the service process where your ASP.NET application is located in the "Process Pool" folder, right-click and select the "Properties" item, as shown in the two pictures below. I don't need to talk nonsense about the rest.
In addition, there is another way to make IIS6.0 the same as IIS5.0, using the settings in the <processModel...> section of the machine.config file to control the ASP.NET service process. (See the previous article for details)
Also open "IIS Manager", right-click the "Website" folder, select the "Properties" item, as shown below, and check "Run the Web service in IIS5.0 isolation mode":
In this way, the behaviors of IIS6.0 and IIS5.0 are exactly the same, and even the name of the ASP.NET service process has changed from "W3WP.exe" to "ASPNET_WP.exe". However, this approach is completely reversing the direction of history. If there is no ulterior purpose, it is definitely not recommended.