To expand on what foosnazzy said, .NET 3.5 (SP1) is just .NET 2.0 SP2 with some new builds. The only reason not to install it on a website is if the website will not work with .NET 2.0 SP2.
This is very different from what it used to be: installing .NET 1.1 on the .NET 1.0 website, which I was responsible for violating the website, even though the website did not use 1.1 - I installed 1.1 so i could use a specific tool. Upgrading from .NET 1.1 to .NET 2.0 is an even worse nightmare.
But Microsoft found out about this ... NET version 2.0. NET 3.5 SP1 uses the .NET 2.0 Common Language Runtime (CLR). In fact, people who installed 3.5 are often surprised to see IIS settings and see that their websites still appear to be running on .NET 2.0. But this is the same .NET 2.0, with only two service packs. Any site that does not use new builds cannot be affected at all (besides what the service pack can do).
To repeat this, C # 3.0 features are independent of the Framework. For example, you can use anonymous types and lambdas in pure .NET 2.0 code. What you cannot do is use LINQ, as this requires new assemblies in .NET 3.5.
John saunders
source share