IIS7 Application Pool Detailed resolution _ Practical tips

In IIS 7, adding an application or a separate Web site automatically creates a corresponding " application pool " By default, which is also a feature of IIS 7.

In the early IIS 5.0, there was only one application pool, and it was easy to create a "annihilated, a glorious loss". Because all Web sites (or applications under the virtual directory) are "resident" in a "pool", when the "pool" crashes, all the sites are cups.

Later in IIS 6, with the concept of "application pool," the default is not automatically added, IIS administrators can manually add, configure, so that IIS is highly isolated.

Application pools have the following benefits:

Improved server and application performance. For applications that are heavily resource-intensive, you can assign them to their own application pools to avoid affecting the performance of other applications.

Improved application availability. If an application in an application pool fails, it will not affect applications in other application pools.

Improved security. Isolating an application reduces the chance that one application can access other application resources.

In IIS 7, the application pool has two modes of operation: Integrated mode and Classic mode. The application pool pattern affects how the server handles requests for managed code. If the managed application is running in an application pool with integrated mode, the server will use the integrated request processing pipeline of IIS and asp.net to process the request. However, if a managed application is running in a classic-mode application pool, the server continues to route managed code requests through aspnet_isapi.dll, and it processes the request as if the application were running in IIS 6.0.

Most managed applications should be able to run successfully in an application pool with integrated mode, but they sometimes need to run in Classic mode to achieve version compatibility. Applications that run in Integrated mode should be tested first to determine if Classic mode is really needed. When deploying a asp.net MVC application with IIS 7, you only need to select "Integration", which does not require the cumbersome configuration in IIS 6 (setting up ISAPI mappings, adding wildcard characters ...). ）