Professional ASP.NET 3.5 Security, Membership, and Role Management with C# and VB

7.5. Serving Classic ASP in IIS 7.0 Integration Mode

The preceding sections emphasized how to define a wildcard mapping for an application that is hosted inside IIS 7.0 and running under the classic .NET application pool that resembles that of the IIS 6.0 functioning mode. As you can see, it was obvious that the process of serving classic ASP pages in an ASP.NET application has not changed at all. You still need to define a wildcard mapping so that the .asp pages are processed by the ASP.NET ISAPI extension before IIS 7.0 takes back control on those resources.

Chapter 2 explained in depth the details of the new IIS 7.0 Integration mode. The discussion will not be repeated here; however, refreshing your memory with the major concepts behind the new integration mode should be helpful.

With the new IIS 7.0 Integration mode, ASP.NET unites with the IIS request pipeline and hence the name integration! Prior to IIS 7.0, a request used to pass through the IIS request pipeline where a set of events would be fired and handled by core native modules inside IIS only. Once IIS finishes its processing on the request, it is handed off to the correct ISAPI extension configured at the level of IIS. Assuming an .aspx page was requested, the ASP.NET engine starts its own managed request pipeline to serve the request and generate a response to be sent back to IIS in order to be sent back to the client making the request.

Now things have changed drastically! The IIS and ASP.NET request pipelines ...