Is the C# 2.0 to C# 3.0 transition worth it for this project? [closed]

Answer 1

It really depends on what you need to do. If your project requires Lambda Expressions where you're query objects with a clear syntax, you should look at 3.0.

I am currently reading C# In Depth by Jon Skeet, and he takes the approach of laying out a solution in C# 1.15, then evolves the solution to depict the new and useful functionality that you get in 2.0 and 3.0. This type of progression would be a perfect means to answer your questions. The book reads well too so I am finding I am getting through it quickly.

Answer 2

You have to weigh cost versus benefit. You don't provide enough information about your project to allow us to advice you here, but consider:

• cost of conversion is pretty small. C# 3.0 is almost completely backwardly compatible with 2.0 and run on framework 2.0
• benefit is also pretty small if the coding is almost finished, but might grow in the long run. A new feature you might have to implement in the future might turn out to be much easier implemented using Linq, for example.

Answer 3

Clarification
C# 3.5 doesn't exist. There is C#1.0, C#2.0 and C#3.0.

Then there is .NET 1.0, .NET 1.1, .NET 2.0, .NET 3.0, and .NET 3.5.

We should not confuse the two.

C# 3.0 vs C#2.0
Now, is C#3.0 worth the move? I would say that with the existence of Extension methods and Lambda expressions, the answer is yes. These two features alone make for easier to read and quicker to write code. Add that to auto-implemented properties, LINQ, and partial methods, and C#3.0 shows itself to be an advantageous move.

However, it is not necessarily beneficial to move an existing project. You have to weigh the pros and the cons, especially with regards to introducing new bugs and instability, before deciding to migrate existing work. For new projects, I'd say start with C#3.0.

Answer 4

3.5 builds on top of 2.0, so you have no issues jumping directly to 3.5.

Answer 5

I've made the conversion many times. Mostly because the clear syntax from lambda expressions makes the code easier to follow (for me anyway).

I do use ReSharper which makes using new 3.5 features a snap as quite a few show up as refactoring suggestions by ReSharper. Using a tool like that makes this transition so much easier.

Answer 6

If you have an extension to the project, it might be a good thing to switch now to the newest version of .NET, otherwise I wouldn't.