integrated-pipeline-mode

I searched high an low and still cannot find a definite answer. How do I configure IIS 7.0 or a Web Application in IIS so that ASP.NET Runtime will handle all requests -- including ones to static files like *.js , *.gif , etc? What I'm trying to do is as follows. We have kind of SaaSy site, which we can "brand" for every customer. "Branding" means developing a custom master page and using a bunch of *.css and other images. Quite naturally, I'm using VirtualPathProvider , which operates like this: public override System.Web.Hosting.VirtualFile GetFile(string virtualPath) { if(PhysicalFileExists

Generally we should have control of our AppPools and be able to force the Managed Pipeline Mode. In my case I don't have control and would like to implement the code behind code a little differently based on the Managed Pipeline Mode (Integrated vs Classic). I just don't know how to detect this. Is there a simple way to do it from within the code behind page? Look at ApplicationPool.ManagedPipelineMode and ServerManager.ApplicationPools Properties. So you can examine ApplicationPool.ManagedPipelineMode of the current AppPool about like this example do, but to do this for ApplicationPool of

I'm having troubles with a custom Error handler I built. It should be a HttpModule , but when I add it to my web.config 's system.webServer/modules tag, it is not initiated. This is my web.config section: <system.webServer> <modules> <add name="AspExceptionHandler" type="Company.Exceptions.AspExceptionHandler, Company.Exceptions" preCondition="managedHandler" /> </modules> </system.webServer> This is the code in my HttpModule : using System; using System.Web; using Company.Settings; using System.Configuration; namespace Company.Exceptions { public class AspExceptionHandler : IHttpModule {

Firstly there's a great overview of the IIS7 HTTP request lifecycle and various settings that affect performance here: ASP.NET Thread Usage on IIS 7.0 and 6.0 Very specifically though, in dotNet 4 the defaults for maxConcurrentRequestsPerCPU and requestsQueueLimit are set to 5000. E.g. equivalent to: (in aspnet.config): <system.web> <applicationPool maxConcurrentRequestsPerCPU="5000" maxConcurrentThreadsPerCPU="0" requestQueueLimit="5000" /> (** see note below) </system.web> Seems to me that on a multi-CPU/core server the requestQueueLimit here will always be invoked well berfore the 'perCPU'

IIS 7.5 Windows 7 64-bit .NET 4.0 I have a .NET 4.0 site in IIS 7.5. The Default Document is set to home.aspx. If the application pools managed pipeline mode is set to "Classic" http://localhost/mysite displays the following error Server Error in '/mysite' Application. -------------------------------------------------------------------------------- The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is