Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is probably a silly question, but the names are confusing and I can't find a direct answer. There are a lot of limits in the ASP section of the IIS configuration that I might want to tweak (such as bufferingLimit, maxRequestEntityAllowed, and queueTimeout) -- but only if they affect ASP.NET.

But I suspect that they don't. Is this correct? Are ASP and ASP.NET entirely different entities as far as IIS 7.5 is concerned?

share|improve this question
up vote 2 down vote accepted

ASP and ASP.NET settings are treated as separate entities. ASP is considered "Classic ASP" and is more of a server-side scripting method -JScript/VBScript-. ASP.NET relies on the .NET Framework -it is compiled-, and ASP.NET applications run in their own AppPool's.

The answer would be "yes."

share|improve this answer

Yup, entirely different. Something applying to system.webServer/asp will not affect system.web or system/webServer (any other section) settings in the slightest.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.