Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I'm just trying to create a new application pool in IIS7 and specify 3.5 for its framework version. However it only has "v2.0.50727" or "no managed code" as options in the framework version drop down.

How can that be and how can I fix it?

share|improve this question
up vote 11 down vote accepted

This is correct.

As long as you have .net 3.5 installed on the box then .net 3.5 web apps will run.

"ASP.NET 3.5, it is still based on the ASP.NET 2.0 core fundamental. Therefore, there is no new application type(for ASP.NET 3.5) in IIS"

Taken from here: link text

share|improve this answer
Thanks for the info. It seems to me then that the dialog's request for a "framework" version is misleading when its really looking for a runtime version. It would have been better to list all the available frameworks even if that makes no actual difference in some cases. – AnthonyWJones May 7 '09 at 19:27
@Anthony: +1, I agree – pbz May 11 '09 at 15:59

There is no separate version for .NET 3.5, because the core runtime with .NET 3.5 is still v2.0.50727. .NET 3.5 is just extra classes and new compilers layered on top of the 2.0 runtime. Just pick 2.0

share|improve this answer

The above two answers are true. Additionally, note this means there is no reason not to "upgrade" to .NET 3.5 (SP1). As far as existing .NET 2.0 code is concerned, this release is just a service pack (.NET 2.0 SP2 to be precise).

share|improve this answer
+1 for trying to remove the fear of upgrading to .net 3.5 (sp1) – Jimmie R. Houts May 7 '09 at 19:46

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.