.Net Framework version issue

views:

409

answers:

+1 Q:

.Net Framework version issue

Hello everyone,

I am using IIS 7.0 + Windows Server 2008 x64. I have installed .Net Framework 3.5 on my machine, but from IIS 7.0 application pool .Net framework settings, I could only set version to v1.0 or v2.0, why I cannot set to version v3.5 -- which is the latest version of .Net framework I installed on my machine?

thanks in advance, George

+5 A:

There's a difference between the version of the CLR (the latest of which is 2.0) and that of the .NET framework (the latest of which is 3.5).

A related post can be found here:

http://stackoverflow.com/questions/801114/what-is-meant-by-asp-net-version-2-0

Martin Peck 2009-05-13 15:06:24

Cool, so final confirm, 1. since the highest version of CLR is 2.0, then even if we deploy features which uses .Net Framework 3.5 (e.g. WCF), it should run on CLR 2.0? 2. when we configure version in IIS application pool, we configure CLR version other than .Net Framework version?

George2 2009-05-13 15:13:08

I believe that is the case obviously if you are using .NET 3.5 framework classes you need the .NET 3.5 framework installed on the server. From the sounds of it it's unlikely you are you could probably downgrade your project to 2.0.

PeteT 2009-05-13 15:16:07

You'll need the .NET 3.5 bins installed somewhere (in the bin folder, in the GAC, or whatever) but those libraries run in a 2.0 CLR.

Martin Peck 2009-05-13 15:16:21

@petebob796, my question is, could I understand CLR has the runtime and .Net Framework as the development SDK?

George2 2009-05-13 15:17:58

@Martin, so when we configure version in IIS application pool, we configure CLR version other than .Net Framework version?

George2 2009-05-13 15:18:08

+2 A:

Versions 3.0 and 3.5 are just extra dlls ontop of the 2.0 framework. Because of this, you will only see 2.0 as an option in IIS.

AaronS 2009-05-13 15:09:34

1. since the highest version of CLR is 2.0, then even if we deploy features which uses .Net Framework 3.5 (e.g. WCF), it should run on CLR 2.0? 2. when we configure version in IIS application pool, we configure CLR version other than .Net Framework version?

George2 2009-05-13 15:13:55

Correct. For any version of the framework 2.0 or higher, you will select 2.0 in IIS. If you don't have 3.5 installed on the server, and you try to use 3.5 features, you will get errors at runtime saying it can't find the correct libraries.

AaronS 2009-05-13 15:34:50

@AaronS, cool answer.

George2 2009-05-13 15:41:12

+1 A:

.NET Framework 3.x = .NET Framework 2.0 + new features (WPF, WF, WCF, etc.)

So no need to worry. Version selectors in IIS will not show 3.x versions.

NinethSense 2009-05-13 15:12:32

could I understand CLR has the runtime and .Net Framework as the development SDK?

George2 2009-05-13 15:14:30

.NET SDK is another package which you can download seperately. (Same comes with Visual Studio also).

NinethSense 2009-05-13 15:21:48

What in your mind is the differences between CLR and .Net Framework? My understanding is CLR is the runtime, and .Net Framework is the library used at development/runtime. My understanding correct?

George2 2009-05-13 15:24:06

CLR is a part of .NET Framework..NET Framework is a library basically. (just like JVM for Java, if you know). Please read: http://en.wikipedia.org/wiki/.NET_Framework

NinethSense 2009-05-13 15:28:29

so when we configure version in IIS application pool, we configure CLR version other than .Net Framework version?

George2 2009-05-13 15:29:19

I like the wiki document you recommended.

George2 2009-05-13 15:39:57

Yes, CLR Version.CLR Version is stil 2.0. Check this link. There is a tabular data which may be more clear for you - http://weblogs.asp.net/rosherove/archive/2006/06/15/MappingCLRWinfxandNETFramework30upcomingversions.aspx

NinethSense 2009-05-13 15:43:18

+1 A:

All IIS cares about is the version of the CLR, not the version of the libraries that you may or may not be loading onto your machine. So it will only show the difference versions of the CLR and not the different versions of the various libraries.

JaredPar 2009-05-13 15:13:00

1. could I understand CLR has the runtime and .Net Framework as the development SDK? 2. since the highest version of CLR is 2.0, then even if we deploy features which uses .Net Framework 3.5 (e.g. WCF), it should run on CLR 2.0?

George2 2009-05-13 15:15:11

+1 A:

To answer the comment that George2 has left to each of the other answers in one place:

Yes. The Common Language Runtime is what needs to be 2.0 (and cannot, currently, be higher, since that's the latest at this time).

Yes. You can think of the .Net Framework as the SDK if that makes it easier. It's not quite accurate, but....

Yes. You will be deploying your Framework 3.5 functionality on the CLR 2.0. Confusing, but that's Microsoft for you. They do (some) great work, but seem to delight in confusing users with arbitrary versioning.

RolandTumble 2009-05-13 15:31:39

There is one left you not answered. :-) question is -- so when we configure version in IIS application pool, we configure CLR version other than .Net Framework version?

George2 2009-05-13 15:33:25

Yes. You configure IIS for the CLR version rather than the Framework version.

RolandTumble 2009-05-13 15:37:11

Cool, question answered.

George2 2009-05-13 15:39:31

ansaurus

tags:

views:

answers:

.Net Framework version issue

related questions