Among other things this attribute is set to classic Mode, which ensures that this handler mapping only takes effect when the application pool is configured to run in classic mode.Now if you want to configure wildcard mapping for the ASP. NET wildcard handler mapping in IIS 7 is subject to the same performance limitations as existed in IIS 6. Because of these performance limitations it is recommended that you use IIS 7 integrated pipeline to achieve the same functionality as with wildcard mappings in IIS 6. NET functionality is fully integrated into the main request processing in IIS, which means that all ASP.The big benefit of IIS 7 integrated request processing pipeline is the fact that all the nice and useful ASP. NET SQL-based membership can be used to protect static files and folders. NET extensibility API’s, such as IHttp Handler and IHttp Module can be used to add custom modules and handlers that would be executed even for non-ASP. This wildcard script map configuration is typically done within IIS 6 manager by opening the properties dialog for either web server or web site and selecting Home Directory tab, then clicking on Configuration button and then clicking on the Insert button for “Wildcard application maps”: Now, as you move your application to IIS 7, you want to configure it to achieve the same behavior of ASP. There are two options on how this can be done: using Classic pipeline mode or using Integrated pipeline mode. NET is plugged into the IIS request processing pipeline as an ISAPI extension – exactly the same way as it was in IIS 6.
This post explains how an application that used wildcard script mapping in IIS 6 can be migrated over to IIS 7. NET in IIS 6 to handle all requests by using wildcard script mapping. NET module for URL rewriting and you wanted this module to handle extension-less URLs. NET was plugged into IIS 6 as an ISAPI extension and by default was configured to handle ONLY requests mapped to that extension – for example any request that ended with “.aspx” would be be processed by ASP. This obviously was a big limitation for customers who wanted to be able to use ASP. The most common way to workaround that was to use “Wildcard script mapping”.NET running in classic mode, you can add one more handler mapping to the The relative order of the wildcard handler mapping is important: if you define this handler mapping after the “Static File” handler mapping then “Static File” will handle all the requests and no requests will ever come to ASP. The problem with this kind of handler mapping is that ALL requests are processed by it, including requests for static files. NET static file handler is not as powerful as native IIS static file handler. NET features are now available for any type of requests. For example let’s say you had a URL rewriting module written in ASP. On IIS 6 this module was registered inside of the .This effectively eliminates the need for the wildcard handler mapping. If you wanted it to handle extension-less URLs you had to configure wildcard script mapping for ASP. With IIS 7 integrated pipeline you do not have to do that anymore.Another benefit of registering your module this way is that now it can be applied to requests for PHP, ASP or any other dynamic pages.
You would not be able to do that if you used wildcard script mappings.