views:

57

answers:

3

We've been developing apps since .NET 2 release and now we are planning to upgrade to .NET 3.5. What is the best approach upgrading from .NET 2.0 to 3.5?

BTW ... the external components that we use are:
1. EntitySpace - ORM
2. Microsoft Enterprise Library
3. Microsoft ReportingViewer 9.00
4. Telerik ASP.NET Controls

+4  A: 

.NET Framework 3.5 is a superset of .NET Framework 2.0. You shouldn't have to do anything except re-target your build output. If any third party components require .NET 2.0 then it will have to still be installed on the target machine.

Mitch Wheat
Just to clarify this, eventhough the third party is built for .NET 2 ... I am still be able to use this?!?!
dewacorp.alliances
+3  A: 

.NET 2.0 and 3.5 Share the same version of CLR (2.0). What .NET framework 3.5 is just .NET 2.0 with a bunch of added lib for WCF, WPF, Linq ....

you shouldn't have any problems.

Keivan
+1  A: 

As others have said, the upgrade is pretty much trivial, but you may have to change some code, because some library methods may have been deprecated. (Well, you won't have to, you'll just get warnings about it.)

Evgeny