Looking For Summary of .NET 2.0 vs 3.5 + VS2k8

[Logan S.]

I have been googling this and have found a few articles, but I'd like to
find something a bit more concise than what I have found.

I would like a list of specific major enhancements between .NET Framework
2.0, 3.0, and 3.5. I'm looking for specific capabilities beyond the
statement, ".NET 3.0 is 2.0 + extra libraries". While true, that misses
specific enhansements.

I'm looking for the same between Visual Studio 2005 and 2008.

Ideally it would be a bullet-point sort of list. Any links you can provide
would be greatly appreciated.

The big picture here is that I have a new client who is still using .NET 2.0
and VS 2005. They/we want to go to 3.5/2008, but we need to put together a
list of specific benefits as part of the migration process and timing of the
switch.

Thanks!

 

[Norman Yuan]

I would be supprised that you cannot find out such information easily.

Do not confuse .NET framework with VS2005/8.

Even your client or you decide to do development with .NET2.0, you can still
use VS2008 (unless you need to do SQL Server 2005 Reporting Services
development: you need VS2005 or BIStudio2005 installed).

Ask yourself, do you need WCF/WWF/WPF in your new development and capable of
programming with them? If not, you can use either VS2005 or VS2008
(targeting .NET2.0). If yes, you need VS2008, and the user need .NET3.x
installed.

 

[MBUnit]

I have been googling this and have found a few articles, but I'd like to
find something a bit more concise than what I have found.

I would like a list of specific major enhancements between .NET Framework
2.0, 3.0, and 3.5. I'm looking for specific capabilities beyond the
statement, ".NET 3.0 is 2.0 + extra libraries". While true, that misses
specific enhansements.

I'm looking for the same between Visual Studio 2005 and 2008.

Ideally it would be a bullet-point sort of list. Any links you can provide
would be greatly appreciated.

The big picture here is that I have a new client who is still using .NET 2.0
and VS 2005. They/we want to go to 3.5/2008, but we need to put together a
list of specific benefits as part of the migration process and timing of the
switch.

<http://msdn.microsoft.com/en-us/library/bb386063.aspx>
<http://davidhayden.com/blog/dave/ar...namicDataFieldsASPNETDynamicDataWebsites.aspx>

This is the big one as far as I am concerned, fabulous.
<http://en.wikipedia.org/wiki/ADO.NET_Entity_Framework>

Also, there are partial functions with the same principles of working
like partial classes.

I am sure you'll find some other stuff too.