tags:

views:

637

answers:

1

hi, i wonder what are the pitfalls of not adapting it, as i am facing many problems with integrated mode. for example URLRewritng.net is not parsing Arabic query string with integrated mode, plus many other problems.

better yet question that is their ability to combine both from web.config, i mean let some HTTP handlers and modules function in mode that suits it ?

thanks in advanced.

+3  A: 

The main advantage with IIS7's integrated mode seems to be native .NET integration into the HTTP request/response pipeline.

Native integration gives you access to each and every request, even for static files, and requires no configuration on the server itself just a setting in the configuration file, something which makes shared hosting easier.

In IIS6 it was possible to integrate .NET into the pipeline by using a wildcard mapping (*) which basically gave you most of the advantages of IIS7 Integrated Mode, even though it's been said that wildcard mapping degrades performance, no one seemed to have specific numbers and this SO question actually shows that performance is not impacted at all.

I don't think it's worth the effort to change your code just to support Integrated Mode, stick to Classic Mode and turn on wildcard mapping if necessary.

James Couvares
thanks a lot man for the great explanation, but i am using IIS 7 in shared hosting environment.when exactly i need the wild card mapping ?
You only need wildcard mapping if you want to process requests without an .aspx extension in the URL (or .asmx .axd etc...) This lets you process static files (.gif .jpg etc...) which can be useful if you want to add authentication to them.
James Couvares
thanks alot man for the help