We have some applications that are being worked upon in .Net 2.0 since long back. I'm recommending my team to move the base from .net 2.0 to .net 3.5sp1 and focus and leverage from C# 3.0 but I'm facing difficulties in doing so. What are the implications of not migrating to .net 3.5 and C# 3.0 ? What are your experiences on this front and what tactics did you use to successfully migrate your team and projects to .net3.5.
A:
Recent SO question: What is the best approach upgrading from .NET 2 to 3.5?
Mitch Wheat
2010-05-05 06:58:02
Should be a comment, I suppose.
Srikanth Venugopalan
2010-05-05 07:07:11
why is that? ...
Mitch Wheat
2010-05-05 08:05:55
Well, the reference you've given doesn't have an accepted answer, I dont know, but seems to me a comment to the question would have helped others notice the link easily.
Srikanth Venugopalan
2010-05-05 08:44:36
+2
A:
There really isn't too much implications with staying in .NET 2.0 land, other than missing out on some improved framework additions liek LINQ to SQL, LINQ to Objects, WCF, WPF etc...
Plus some fun syntax features like anonymous methods, lambda expressions, and extension methods.
Moving to .NET 3.5 is really straight forward. Hats off to the team at MSFT. They made the process very painless.
Alan
2010-05-05 07:06:01
The benefits of the new language features in the C# 3.0 compiler are priceless. And since all that runs on the .NET 2.0 runtime (if you deploy System.Core.dll for the LINQ extension methods) you would miss a lot if you wouldn't do this step.
Sebastian P.R. Gingter
2010-05-05 07:59:29
Just a small nit-pick but anonymous methods will work in 2.0 as long as you compile with 2008. The same goes for auto-implemented properties and object initializers.
ParmesanCodice
2010-05-05 08:51:06
+1
A:
I'd do a two-step migration. First I'd migrate to C# 3.0, while sticking with .NET 2.0. You get most of the benefits of C# 3.0 (including LINQ to Objects via LINQBridge). Once the developers have shifted their mindset to that of LINQ and lambda expressions, fallen in love with extension methods, beautified their code with automatic properties and got hooked on the rest of C# 3.0 features, I'd migrate the application to the .NET Frameworks 3.5 SP1 (which should be effortless, like others have mentioned).
Allon Guralnek
2010-05-05 07:54:19