Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m currently working on an client application developed using winforms on .Net 2.0. Are there any reasons I should upgrade to 3.5? I already use LINQ (with linqbridge) and I can think of no other benefits I would get from 3.5 (I will not start using WPF or a new data access technology …)
Does your application need to use time zones at all?
TimeZoneInfois vastly better than the pre-3.5 alternatives.If you only need LINQ to Objects, then with LINQBridge you should be mostly okay. Of course you may come across non-LINQ situations where you’d benefit from expression trees, but they’re relatively rare.
If you’ll find deployment easier with .NET 2.0 SP1, then by all means stick with it. That’s not to say there aren’t nice things in .NET 3.5, but if you don’t want to use WCF, WPF etc then a lot of those benefits won’t be applicable to you.