Porting an application from dotnet 2.0 to 3.5

Question

Is there any documentation about the changes that may occur when porting an application from dotnet 2.0 to 3.5. His understanding is that this is actually not a major change in runtime, but rather the addition of many new libraries (LINQ, etc.). Assuming I'm right, should I change any 2.0 code to compile to 3.5. My concern than compiling time gaps is all that compiles fine, but subtly works differently.

Answer 1

.NET 3.5 adds many new builds, but the main runtime is 2.0. Or it’s actually 2.0 SP1, so in very rare cases you can see the differences, but in most cases you don’t have to do anything.

Here is a useful overview of wikipedia versions .

Answer 2

The simple answer is that switching the target application runtime should not lead to impaired functionality.

Answer 3

, . , . 1 3.5, SQL CE, .

Answer 4

, 3.5 2.0. 2.0 , , , 2.0.
, , , 2.0 3.5 , 2.0, - MethodMissingException , .