IIS中的經典模式和集成模式有什么區別

平時哪管它有什么區別，經典模式不行就集成模式啊。什么？都不行啊。根據報錯信息網上找解決方案啊，沒有？不會問人嗎？不過，現在正好有時間，可以自己了解下。為了避免曲解，還是閱讀英文為宜。

IIS 6.0 and PRevious versions allowed the development of .NET application components via the asp.net platform. ASP.NET integrated with IIS via an ISAPI extension, and exposed its own application and request processing model. This effectively exposed two separate server pipelines, one for native ISAPI filters and extension components, and another for managed application components. ASP.NET components would execute entirely inside the ASP.NET ISAPI extension bubble and only for requests mapped to ASP.NET in the IIS script map configuration.

IIS 7.0 and above integrates the ASP.NET runtime with the core web server, providing a unified request processing pipeline that is exposed to both native and managed components known as modules. The many benefits of integration include:

• Allowing services provided by both native and managed modules to apply to all requests, regardless of handler. For example, managed Forms Authentication can be used for all content, including ASP pages, CGIs, and static files.
• Empowering ASP.NET components to provide functionality that was previously unavailable to them due to their placement in the server pipeline. For example, a managed module providing request rewriting functionality can rewrite the request prior to any server processing, including authentication.
• A single place to implement, configure, monitor and support server features such as single module and handler mapping configuration, single custom errors configuration, single url authorization configuration.

Learn more about building IIS 7.0 and above modules in Developing IIS 7.0 and Above Modules and Handlers with the .NET Framework.

英文部分內容鏈接在這里。這里不是經典模式和集成模式的區別，而是IIS不同的版本之間的區別，IIS7.0對內部的處理方式（如Request請求特別是認證）做了一些改變，或者可以理解是為了解決以前版本設計的不足或者優化，但是又要保證和以前的IIS完全兼容，所以給兼容Legacy IIS取了一個選擇項名字，叫做“經典模式（Classic Mode）”。改進后的（IIS 7.0）取個選擇項名字叫做“集成模式（Integrated Mode）”。或許用的更多理解會更加深刻的。