Skip to content

IIS 7 Configuration: Classic vs. Integrated mode

8 Apr, 12

Question:

Yesterday in the quiz during “Reliving TechEd India 2012” event, Vinod Kumar M, asked one question and asked to tweet the answer. While searching the answer I found it more interesting and wrote below post on that.

The question was: What is the new capability in Integrated mode that classical mode does not support in IIS 7?

Answer:

(In Short): As Integrated mode allows ASP.NET modules to participate in IIS request processing regardless of the type of resource requested so ASP.NET services (such as Forms authentication, roles, URL authorization, and output caching) can be applied to all requests (including requests for Static files, ASP pages, and other content types which was not possible in classic mode).

Description:

Web applications in IIS 7.0 can be configured to use either Classic mode or Integrated mode. Classic mode maintains backward compatibility with earlier versions of IIS by using an ISAPI extension to invoke the ASP.NET runtime. This option usually requires few or no modifications to existing applications.

Classical Mode:

Classic mode uses the IIS 6.0 processing pipeline for hosting ASP.NET applications. In this mode, requests are processed initially through IIS 7 modules, and ASP.NET requests are further processed by the aspnet_isapi.dll. The ASP.NET processing pipeline is separate from the IIS 7 processing pipeline, and the ASP.NET request processing pipeline features are not available to other resource types. This also means that an ASP.NET request must pass through authentication and authorization modules in both process models. While this is not as efficient as Integrated mode, it does allow you to run applications developed using ASP.NET version 1.1 on an IIS 7 server without modifying the application to run in Integrated mode.

Integrated mode:

IIS 7.0 Integrated mode is a unified request-processing pipeline that combines the ASP.NET request pipeline with the IIS core request pipeline. The integrated pipeline provides improved performance, provides modularity for configuration and administration, and adds flexibility for extending IIS with managed-code modules.

Integrated mode allows IIS to process requests in the application pool by using the IIS 7 integrated pipeline. This allows ASP.NET modules to participate in IIS request processing regardless of the type of resource requested. Using integrated mode makes available features of the ASP.NET 2.0 request pipeline available to requests for static content, as well as ASP, PHP and other content types. By default, IIS 7 application pools run in this mode.

Source:

http://learn.iis.net/page.aspx/243/aspnet-integration-with-iis/  …….Very descriptive and best source

http://msdn.microsoft.com/en-us/library/bb515251.aspx

http://www.iis.net/ConfigReference/system.applicationHost/applicationPools

Thanks for reading. Have a nice time.

From → ASP.NET

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: