The document discusses the history and features of different versions of the .NET framework. It describes .NET Framework versions 2.0, 3.0, 3.5, and 4.0, noting what each version introduced and the operating system support for each. The .NET Framework versions 2.0, 3.0, and 3.5 use the same CLR 2.0 and build incrementally on each other, while version 4.0 introduced a new CLR and allows side-by-side installation of multiple framework versions. Each version is suited for different development and deployment needs depending on required features and supported operating systems.

1. More about .NET Frameworks

2. Learning Objectives Overview
Lecturer: Jareed Eve;2
 .NET Framework Versions History
 .NET Framework Versions and Dependencies
 .NET Framework Versions
 Version 2.0
 Version 3.0
 Version 3.5
 Version 4.0

3. .NET Framework Version History
Lecturer: Jareed Eve;3
 The .NET Framework versions 2.0, 3.0, and 3.5 are built with the
same version of the CLR (CLR 2.0).
 These versions represent successive layers of a single
installation.
 Each version is built incrementally on top of the earlier .NET
Framework versions.
 It is not possible to run versions 2.0, 3.0, and 3.5 side by side on
a computer.
 When you install the .NET Framework 3.5 SP1, you get the 2.0
and 3.0 layers automatically.
 However, the .NET Framework 4 ends this layering approach.
Starting with the .NET Framework 4, you can use in-process
side-by-side hosting to run multiple versions of the CLR in a
single process. Apps that were built for versions 2.0, 3.0, and
3.5 can all run on version 3.5, but they will not work on
version 4 or later.
 The .NET Framework 4.5 is an in-place update that replaces the
.NET Framework 4 on your computer. After you install this
update, your .NET Framework 4 apps should continue to run
without requiring recompilation.

4. Lecturer: Jareed Eve;4

5. Features Overview
Lecturer: Jareed Eve;5
.NET
Versio
n
Description
2.0 Introduced a new version of the CLR with additions to the base
class libraries, including generics, generic collections, and
significant additions to ASP.NET. This version was updated with
SP1 and SP2.
3.0 This version is essentially .NET Framework 2.0 with the addition
of Windows Presentation Foundation (WPF), Windows
Communications Foundation (WCF), Windows Workflow
Foundation (WF), and CardSpace. It was updated with SP1 and
SP2.
3.5 Added new features such as AJAX-enabled websites and
LINQ. The SP1 update added Dynamic Data, and a small set of
additional enhancements.
4.0 Included a new version of the CLR, expanded base class
libraries, and new features such as the Managed Extensibility
Framework (MEF), dynamic language runtime (DLR), and code

6. Operating System Support -
Client
Lecturer: Jareed Eve;6
Client OS Includes You Can Also Install
Windows 8 .NET Framework 4.5 .NET Framework 3.5
SP1
Windows 7 .NET Framework 3.5
SP1
.NET Framework 4.5,
.NET Framework 4
Windows Vista SP2 .NET Framework 3.0
SP2
.NET Framework 4.5,
.NET Framework 4,
.NET Framework 3.5
SP1
Windows XP
Professional and
Windows XP Home
Edition
.NET Framework 4,
.NET Framework 3.5
SP1,
.NET Framework 2.0
SP2

7. Operating System Support -
Server
Lecturer: Jareed Eve;7
Server OS Includes You Can Also Install
Windows Server 2012 .NET Framework 4.5 .NET Framework 3.5
SP1
Windows Server 2008
R2
.NET Framework 2.0
SP2 (enabled by
default),
.NET Framework 3.5
SP1*,
.NET Framework 3.0
SP2*
.NET Framework 4.5,
.NET Framework 4
Windows Server 2008
SP2
.NET Framework 2.0
SP2 (enabled by
default),
.NET Framework 3.0
SP2*
.NET Framework 4.5,
.NET Framework 4,
.NET Framework 3.5
SP1
Windows Server 2003 .NET Framework 2.0
SP2
.NET Framework 4,
.NET Framework 3.5

8. Lecturer: Jareed Eve;8

9. .NET Framework: Version 2.0 (2005)
Lecturer: Jareed Eve;9
 Most modern computers out there will have this
installed already.
 This is also a great version of the framework to
choose if you’ll be supporting Mono (which allows
your code to run on a variety of devices and operating
systems, including Linux and MacOS).
 http://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_
2.0
Why use this?
 Your application must support Windows 98,
Windows ME, or Windows 2000.
 You want to avoid requiring .NET Framework
updates as part of your deployment process as
much as reasonably possible.

10. .NET Framework: Version 3.0 (2006)
Lecturer: Jareed Eve;10
 .NET 3.0 is actually not a full release of the .NET
Framework.
 It’s really just .NET 2.0 plus some new technologies
thrown in (WPF, WCF, WF and a few other oddities).
 This version was included with Windows Vista, but
was never really popular with developers.
 http://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_
3.0
Why use this?
 You require features not available in .NET 2.0
 Your application must not require Framework
updates
 Your application will only run on Windows Vista or
newer.

11. .NET Framework: Version 3.5 (2007)
Lecturer: Jareed Eve;11
 It’s really just good old .NET 2.0, plus a bunch of
changes and additions.
 As a developer, there’s a lot of new stuff here since
2.0 (LINQ is introduced, WCF and WPF are a bit
more usable, ASP.NET includes AJAX support, and
there are a bunch of other new toys and language
improvements to play with).
 http://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_
3.5
Why use this?
 You require features not available in .NET 2.0
 Your application must not require Framework
updates
 Your application will only run on Windows 7

12. .NET Framework: Version 4.0 (2010)
Lecturer: Jareed Eve;12
 This is the first true update to the CLR since .NET 2.0
was released.
 It includes all the developer magic released in 3.5,
adds more toys and polish, brings some very
welcome language improvements, improves
performance and security, makes WCF usable,
makes WPF almost bearable, and generally makes
life much happier for everyone.
 Side-by-side installation with previous versions works,
and works well.
 http://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_
4
Why use this?
 Parallel computing, multi-core or distributed systems
 You don’t need to support pre-WinXP machines.
 You don’t mind requiring your users to install a (simple
and easy) framework update.

13. END
Lecturer: Jareed Eve; Course: OOSD13