Porting existing code from C # 2.0 to C # 3.0 and .Net 3.5 (possibly .net 4.0)

Question

Our one and only set of enterprise applications has been developed over the past 3 years using C # 2.0 on .Net 3.0. We use winforms and WCF. Development Tools - This is VS 2005 Pro / TFS 2005 / Resharper 3.1

As a technical conclusion, I obviously understand the benefits of migrating to C # 3.0 and .Net 3.5. But I want to convince management of the transition to C # 3.0, .Net 3.5, VS 2008 and TFS 2008. Obviously, they will be interested in such things as performance, cost, quality, etc. Please offer me some ideas on how best to make my case.

Given that this can happen before the middle of next year, I better spend up to VS 2010 and .NET 4.0.

Answer 1

"If we don’t move on to new technologies, it will be harder to hire good developers, and those we already have will disappear soon ... maybe including me ..."

Answer 2

How much is there in .NET 4.0 that will benefit you? C # 4 itself does not have many new features ... while I expect that you will be able to make good use of C # 3 functions. .NET 4.0 has very interesting things (in particular, contracts with code and parallel extensions), but you must really see what you will use.

, VS2008 # 3, .NET 2.0. ( # 3 - .NET 2.0.) LINQBridge, LINQ to Objects, .

, .NET 3.5, LINQ ..

Answer 3

• Microsoft , , .
• , Linq-to-Entities. ORM, .
• , . . . , , .
• 5 ", ". ?
• . . .
• . X. . " XYZ NN, MM ".
• . "" -. " , ", . , , , , , .

: , , , , , , .

Answer 4

, , # 2.0 # 3.0, . , , , ?

• VS2005 VS2008 -. VS2005, , , , , VC6. , Microsoft SDL (5.0) VS2008 .

• VS2008 , , . , , .

• / VS2008, # 3.0 # 2.0 .

• VSTS .

Answer 5

# 2.0, LINQ. , .

( ) . .

Answer 6

, - , - . .NET 3.5, 3.5. . , . , / . . (.. 3.5 - ), , , , exceed costs. Otherwise, you may be in a situation in which I found myself.