.Net3.0 and .Net3.5

  • Thread starter Thread starter pinhead
  • Start date Start date
P

pinhead

Can anyone explain what the major differences are between .Net3.0
and .Net3.5, specifically, what are the extra namespaces gained with
3.5?

Most (if not all) of our computers are running .Net3.0 and I'm
wondering what benefits can be gained by deploying 3.5 (and maybe
SP1)?
 
pinhead said:
Can anyone explain what the major differences are between .Net3.0
and .Net3.5, specifically, what are the extra namespaces gained with
3.5?

A lot of stuff, both in 3.5, and then in 3.5 SP1:

3.5 - http://msdn.microsoft.com/en-us/library/bb332048.aspx
3.5 SP1 - http://msdn.microsoft.com/en-us/library/cc713697.aspx

To name a few: LINQ (all its various flavors), ADO.NET Data Services,
ADO.NET Entity Framework, System.AddIns, HashSet<T>, DateTimeOffset &
TimeZoneInfo, and some new goodies for ASP.NET (integrated AJAX framework,
ListView control) and WPF.

Of course, there are also all the new language features in C# 3.0 and VB9,
but those are strictly speaking distinct from framework versions.
 
pinhead said:
Can anyone explain what the major differences are between .Net3.0
and .Net3.5, specifically, what are the extra namespaces gained with
3.5?

Most (if not all) of our computers are running .Net3.0 and I'm
wondering what benefits can be gained by deploying 3.5 (and maybe
SP1)?

In addition to the other replies ...

..Net 3.0 is an add-on to .Net 2.0. It contains three libraries for Windows
Presentation Foundation (WPF), Windows Workflow Foundation (WF) and Windows
Communication Foundation (WCF) (and Windows Cardspace). You can use these in
Visual Studio 2005 by adding extensions.

..Net 3.5 is the next .Net version after 2.0 shipped with Visual Studio 2008
 
Morten Wennevik said:
.Net 3.0 is an add-on to .Net 2.0. It contains three libraries for
Windows
Presentation Foundation (WPF), Windows Workflow Foundation (WF) and
Windows
Communication Foundation (WCF) (and Windows Cardspace). You can use these
in
Visual Studio 2005 by adding extensions.

.Net 3.5 is the next .Net version after 2.0 shipped with Visual Studio
2008

..NET 3.5 isn't really a full-fledged new version - the runtime is still 2.0.
The difference between 3.0 and 3.5 is that 3.0 only introduced new
libraries, while 3.5 also introduced new compilers for C# and VB (and SP1
introduced some minor updates to the runtime, but nothing notable).
 
Pavel Minaev said:
..NET 3.5 isn't really a full-fledged new version - the runtime is still 2.0.
The difference between 3.0 and 3.5 is that 3.0 only introduced new
libraries, while 3.5 also introduced new compilers for C# and VB (and SP1
introduced some minor updates to the runtime, but nothing notable).

That depends on what you define by full-fledged new version. .Net 3.5
changed the .Net core system (although mscorlib has been largely left
untouched for compatibility reasons and new stuff has been put in
System.Core), introduced C# 3.0 and VB.Net 9.0. It does, however, use the
CLR for 2.0, but updates it to handle .net 3.5 stuff.
 
Morten Wennevik said:
It does, however, use the CLR for 2.0, but updates it to handle .net 3.5
stuff.

What updates do you have in mind here? To the best of my knowledge, there is
nothing in .NET 3.5 that requires any changes to the runtime (i.e., you
should be able to take all the new 3.5 libs and run them on top of a plain
2.0 runtime).
 
Back
Top