It seems that 3.5 was a big leap from 2.0. My workplace is still stuck on 2.0. What kind of fun am I missing out on by not being able to upgrade?
+4
A:
You miss, anonymous variable, lambda operator, LINQ (very powerfull), extension-method (very powerfull to) and a lot of features
Cédric Boivin
2009-08-17 13:48:09
2.0 supports anonymous functions
Joel Coehoorn
2009-08-17 13:49:27
+26
A:
A few things off the top of my head:
- Extension methods.
- lambda expressions
- better json serialization support
- linq
- WCF
- WPF
- WF
- collection initializers
- object intializers
- anonymous types
We're still on 2.0 here, as well.
Joel Coehoorn
2009-08-17 13:48:39
Technically, not entirely true. Extension methods just need C#3.0 and can easily be used in .NET 2.0, same goes for collection and object initializers and anonymous types.
Jeff Yates
2009-08-18 14:16:22
Extension methods do require the declaration of an attribute type, but the others do not. Just C#3.0 targetted at .NET 2.0.
Jeff Yates
2009-08-18 14:21:38
A:
It depends on what kind of development you do (windows forms vs. asp.net). Here are some points:
- If you want to use LINQ
- Ajax is integrated in the framework
- webparts drag and drop works in firefox browser
- Also if you want to use other things like micorsoft chart, workflow foundation etc.
There are many other things. Just google on it and you will find lots of links.
Samuel
2009-08-17 13:53:43
A:
Silverlight 3 is targeted at .NET 3.5. You can make apps similar to AIR with it so you can tear an app off of the web page and make it a desktop app. My customers love the silverlight graphs and gauges even when the rest of the app is in regular Ajax ASP.NET.
Stradas
2009-08-17 14:04:38
+2
A:
LINQ
I know it's already been said several times, but in my opinion LINQ (optionally using lambda syntax to make things clearer) has been a game changer - entire modules of code can sometimes be rolled into a single coherent LINQ statement, and the result isn't just easier to write, it's easier to read and maintain because you aren't dealing with mountains of boiler plate code - it's purified, near 100% business logic.
David
2009-08-17 14:17:10
A:
The two biggest things you're missing out on is some libraries. Off the top of my head these are WCF, WPF, ASP.NET MVC. ICBW.
If you need to stay on the .Net 2.0 framework, but can use VS 2008, then you do not miss out on LINQ (LINQBridge), compile time inference, lambdas which is the real squishy chewy goodness of .Net 3.5.
The extra libraries in .Net 3.5 are worth it, and in my experience it has been a painless upgrade. Remember that .Net 3.5 still compiles to .Net 2.0 CLR.
Update The advantage of targetting the .Net 2.0 is more users have .Net 2.0 on their machines than 3.5 SP1. That means they don't have to do a massive download.
John Oxley
2009-08-17 14:29:24