What is the difference between Classic and Integrated in IIS7 Managed Pipeline Mode?

Asked

Viewed 2,883 times

4

I was having a problem generating a Crystal Reports report that was solved when I changed Managed Pipeline Mode to Classic in the Application Pool.

I would like to know the difference between Classic and Integrated in IIS7 Managed Pipeline Mode.

iis iis-7

1 answer

6


Classic mode (the only mode in IIS6 and older versions) is a mode where IIS only works with extensions ISAPI and filters ISAPI directly. Roughly speaking, ASP.NET is just an extension ISAPI (aspnet_isapi.dll) and an ISAPI filter (aspnet_filter.dll). IIS only treats ASP.NET as an external plugin implemented in the standard ISAPI and works with it, as a black box (and only when it is necessary to send the request to ASP.NET). In this mode, ASP.NET is not very different from PHP or other IIS technologies, such as Classic ASP. Obviously it is more limited in a number of things, being discouraged from using if the application is in a Framework above 2.0.

Already the integrated mode is a new mode that appeared precisely in IIS7, where the pipeline IIS is fully integrated with the ASP.NET request channel. ASP.NET can view each request as you wish and manipulate its parts along the way, no longer being treated as an external plugin. In this mode, ASP.NET is basically a part of IIS.

The options are maintained today by mere compatibility scheme, in which companies do not want to modify their systems but want to migrate from Windows platform, for example. Other than that, there is no advantage in using the classic mode.

  • Gypsy, and for applications in ASP, is there a problem in using integrated mode? Or if there is some benefit in using classic mode with ASP?

  • 2

    Problem I believe not, just as there is no advantage. It is only worth worrying about these ways to Dlls do . Older NET, where this was pertinent.

Browser other questions tagged iis iis-7

You are not signed in. Login or sign up in order to post.