I.T. Discussion Community!
-Collapse +Expand
Search Design Group:

-Collapse +Expand Design Store

Prestwood eMagazine

June Edition
Subscribe now! It's Free!
Enter your email:

   ► KBWebsite Hosting   Print This     
  From the November 2015 Issue of Prestwood eMag
Design Website Hosting:
Where is v3.5 of the .NET Framework in IIS configuration?
Posted 11 years ago on 7/16/2009 and updated 5/28/2010
Design Q&A Flashcard:
 A flashcard from our Design Flashcards Library
 A FAQ from our Design FAQ Page



I've created a web application using v3.5 of the .NET Framework.  But, when I go to deploy it, I find only versions 1.x and 2.x in the ASP .NET dropdown for IIS configuration of my application's virtual directory.  Where is v3.5?  How do I deploy if that's not a configuration choice?


It's not there. You see, v3.5 isn't really a "version" in Microsoft's eyes. 3.5 builds upon v2, and is really considered an incarnation of v2.  Sounds crazy, doesn't it? Not to worry, though, you can still deploy your v3.5 app.  There are just two things that must be done:

  1. The .NET Framework, v3.5 must be installed on the server.
  2. When configuring your application's virtual folder in IIS, choose the v2.x from the ASP .NET version dropdown. 

You'll find this in IIS on the ASP .NET tab of the Properties dialog for your app's virtual directory.

Note: I say version 2.x because I'm not sure that all servers will display the same version numbers as displayed on my XP Pro hosted IIS v6.  Mine shows versions 1.1.4322 and 2.0.50727. I choose the latter for the v3.5 projects I'm building and testing.  You'll simply choose whichever v2.x shows up on your IIS.

So how, then, does IIS know which Framework version to use with your app?

IIS looks in your project's web.config file.  If you open your web.config file and scan the first few lines, you'll see many references to v3.5.x.  That's how IIIS knows which framework is required.

You've encountered a bit of the Microsoft madness that provides the fodder for Apple's  great television ads.

For more Microsoft madness, just look into how v8 of Internet Explorer breaks your ASP .NET web applications. It's just crazy.  Claiming to make IE8 much more standards compliant, MS has "broken" many web applications built using Microsoft's own tools.

We have an article about that, too. See the links below.

More Info

Article:  IE8 Combatibility Isn't Compatible


Share a thought or comment...
Write a Comment...
Sign in...

If you are a member, Sign In. Or, you can Create a Free account now.

Anonymous Post (text-only, no HTML):

Enter your name and security key.

Your Name:
Security key = P112A1
Enter key:
FAQ Contributed By Wes Peterson:

Wes Peterson is a Senior Programmer Analyst with Prestwood IT Solutions where he develops custom Windows software and custom websites using .Net and Delphi. When Wes is not coding for clients, he participates in this online community. Prior to his 10-year love-affair with Delphi, he worked with several other tools and databases. Currently he specializes in VS.Net using C# and VB.Net. To Wes, the .NET revolution is as exciting as the birth of Delphi.

Visit Profile

 KB Article #102015 Counter
Since 7/16/2009

Follow PrestwoodBoards on: 

©1995-2020 PrestwoodBoards  [Security & Privacy]
Professional IT Services: Coding | Websites | Computer Tech