Compatibility when upgrading from .net 2.0 to 3.5

Question

At the moment, we are still working with the framework 2.0, and although 2.0 provides everything we need at the moment, we will need to return to 3.5 sooner or later. The other day in the house it was discussed whether there is a risk associated with this update, and this risk should not be taken easily, since all our customers still use the 2.0 structure. There was one colleague who stated that it would be safer to simply recompile all our products compared to framework 3.5 and complete the new release. This will solve any compatibility issues. A lot of work is really and probably not necessary, I believe that Microsoft grants, which provided Microsoft grants, support backward compatibility, why do we have any doubts about this? Am I right about that?

Answer 1

This is not 100% .... most importantly, 3.5 and 3.5SP1 include service packs to 2.0 and (later) 3.0; these changes are not all trivial.

As a key; if you start using types in SP1 even in what you think is 2.0 , it will fail on the “right” client 2.0. There is an FX cop tool to help avoid this, IIRC. Secondly, there are (in the service pack) changes in the depths of the kernel - for example, the number of pool threads (or is it the size of the pool thread stack ... something in this area) that can bite you if you're out of luck.

, 2.0 ; () , (SP1/SP2)...

, ; .NET 3.5, 2.0; -p

, ( ), .

Answer 2

, , , , .net 3.5, .net 2.0 SP1. Hanselman post, ( " " ).

, .

Answer 3

2.0 Framework 3.5, - . 3.5, , 2.0, , IIS .NET -, .NET 2.0, 3.0/3.5 ( ).

, , 2.0, , , IDE VS2008 2.0, 3.5, . , 3.5-, LINQ, .

Answer 4

..NET 3.5 .NET 2.0, . , .NET 3.5 - WinForms - , .

, - (, , ), , , .

Answer 5

, .NET 3.0, 3.5 3.5SP1 . "" .NET 2.0 (CLI, CLR, GC). .NET 3.0 3.5 .NET 2.0. .NET 3.0 3.5 ... .NET 3.5 SP1 .NET 2.0, , ( ) . , , , :

http://forums.asp.net/t/1305800.aspx http://www.hanselman.com/blog/UpdateOnNETFramework35SP1AndWindowsUpdate.aspx