We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

New IIS7 Article: Taking Advantage of the IIS7 Integrated PipelineRSS

0 replies

Last post Jun 09, 2006 01:16 AM by bills

  • bills bills

    415 Posts

    Microsoft

    New IIS7 Article: Taking Advantage of the IIS7 Integrated Pipeline

    Jun 09, 2006 01:16 AM|bills|LINK

    IIS6 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.

    IIS7 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, takes place.
    • A single place to implement, configure, monitor and support server features. For example, single module and handler mapping configuration, single custom errors configuration, single url authorization configuration.

    This article examines how the ASP.NET applications can take advantage of the integrated mode in IIS7, and illustrates the following tasks:

    • Enabling/disabling modules on a per-application level.
    • Adding managed application modules to the server, and enabling them to apply to all request types.
    • Adding managed handlers
    ~~~~~~~~~~~~~~~~~~~~~~~~
    Bill Staples
    Product Unit Manager, IIS
    blog: http://blogs.iis.net/bills