Original address: https://msdn.microsoft.com/en-us/library/bb822049 (v=vs.110). aspx
NET Framework Versions and Dependencies
The. NET Framework (current version)
Other Versions
Each version of the. NET Framework contains the common language runtime (CLR), the base class libraries, and other managed Libraries. This topic describes the key features of the. NET Framework by version, provides information about the underlying CLR vers Ions and associated development environments, and identifies the versions that is installed by the Windows operating Syst Em.
Note
For information on downloading and installing the. NET Framework, see Installing the. NET Framework.
The following table summarizes. NET Framework version history and correlates all version with Visual Studio, Windows, and Windows Server. Note that Visual Studio provides multi-targeting, so-is isn't limited to the version of the. NET Framework. Ed.
Each new version of the. NET Framework retains features from the previous versions and adds new features. The CLR is identified by its own version number. The. NET Framework version number is incremented at each release and although the CLR version is not always incremented. For example, the. NET Framework 4, 4.5, and later releases include CLR 4, but the. NET Framework 2.0, 3.0, and 3.5 include CLR 2.0. (There was no version 3 of the CLR.)
See the. NET Framework System Requirements for a complete list of supported operating systems. For downloads, see the Installation Guide. for determining which version (s) of the. NET Framework are installed on a computer, see how To:determine which. NET Framew Ork Versions is installed.
In the table, the versions marked with * must is enabled in Control Panel (for Windows) or enabled through the Server Mana GER (for Windows Server).
. NET Framework Version
CLR version
Features
Included in Visual Studio version
? Included in
+ Can be installed on
Windows
? Included in
+ Can be installed on
Windows Server
To determine installed. NET version
Net 4.6.1
4
Support for X509 certificates containing ECDSA
Always Encrypted-Hardware protected keys in ADO
Spell checking improvements in WPF
More ...
? Ten November Update
+ 10
+ 8.1
+ 8
+ 7
+ R2
+ 2012
+ R2 SP1
+ SP2
Use Releasedword:
(seeinstructions)
. NET 4.6
4
Compilation using. NET Native
ASP. NET Core 5
Event Tracing Improvements
Support for Page encodings
More ...
Although some. NET libraries is available on NuGet. For more information see, the. NET Framework and Out-of-band releases.
? 10
+ 8.1
+ 8
+ 7
+ Vista
+ R2
+ 2012
+ R2 SP1
+ SP2
Use Releasedword:
(seeinstructions)
4.5.2
4
New APIs for transactional systems and ASP.
System DPI resizing in Windows Forms controls
Profiling improvements
ETW and Stress Logging improvements
More ...
-
+ 8.1
+ 8
+ 7
+ Vista
+ R2
+ 2012
+ R2 SP1
+ SP2
Use releasedword:379893
(seeinstructions)
4.5.1
4
Support for Windows Phone Store Apps
Automatic binding Redirection
Performance and debugging improvements
More ...
2013
? 8.1
+ 8
+ 7
+ Vista
? R2
+ 2012
+ R2 SP1
+ SP2
Use Releasedword:
378675 (Windows 8.1)
378758 (All other)
(seeinstructions)
4.5
4
2012
? 8
+ 7
+ Vista
? 2012
+ R2 SP1
+ SP2
Use releasedword:378389
(seeinstructions)
4
4
2010
+ 7
+ Vista
+ R2 SP1
+ SP2
+ 2003
Seeinstructions
3.5
2.0
ajax-enabled Websites
Linq
Dynamic data
More ...
2008
? 10? 8.1*
? 8*
? 7
+ Vista
? R2 sp1*
+ R2
+ 2012
+ SP2
+ 2003
Seeinstructions
3.0
2.0
-
? Vista
? R2 sp1*
? sp2*
+ 2003
Seeinstructions
2.0
2.0
Generics
ASP. Additions
More ...
2005
-
? R2 SP1
? SP2
? 2003
Seeinstructions
1.1
1.1
ASP.
Side-by-side execution
More ...
2003
-
? 2003
Seeinstructions
1.0
1.0
First version of the. NET Framework.
Visual Studio. NET
-
-
Seeinstructions
In general, you should no uninstall any versions of the. NET Framework is installed on your computer, because an AP Plication depend on a specific version and the May break if the version is removed. You can load multiple versions of the. NET Framework in a single computer at the same time. This means so you can install the. NET Framework without have uninstall previous versions. For more information, see Getting Started with the. NET Framework. Targeting and Running. NET Framework Apps for version 4.5 and later
The. NET Framework 4.5 is a in-place update that replaces the. NET Framework 4 on your computer, and similarly, the. N ET Framework 4.5.1 4.5.2, and 4.6 is in-place updates to the. NET framework 4.5, which means this they use the same runti Me version, but the assembly versions is updated and include new types and members. After you install one of the these updates, your. NET Framework 4 or. NET Framework 4.5 apps should continue to run without re Quiring recompilation. However, the reverse is not true. We do not recommend running apps, the target a later version of the. NET Framework on the. NET Framework 4.5. The following guidelines apply:
-
In Visual Studio, you can choose the. NET Framework 4.5 as the target Framework for a project (this sets the Getreferenceassemblypaths.targetframeworkmoniker property) To compile the project as a. NET Framework 4.5 assembly or EXEC Utable. This assembly or executable can and is used on any computer that have the. NET Framework 4.5, 4.5.1, 4.5.2, or 4.6 install Ed.
-
In Visual Studio, you can choose the. NET Framework 4.5.1 as the target Framework for a project (this sets THEGETR Eferenceassemblypaths.targetframeworkmoniker property) To compile the project as a. NET Framework 4.5.1 Assembly or Execut Able. This assembly or executable should is run only on computers that has the. NET Framework 4.5.1 installed. An executable that targets the. NET Framework 4.5.1 would be is blocked from running on a computer that's only have the. NET Fram Ework 4.5 installed, and the user would be a prompted to install the. NET Framework 4.5.1. In addition,. NET Framework 4.5.1 assemblies should is called from a. NET Framework 4.5 app.
Some changes in the. NET Framework may require changes to your app code; See APP compatibility in the. NET Framework 4.5 before your run your existing apps with the. NET Framework 4.5 or later ver Sions. For more information on installing the current version, see Installing the. NET Framework. For information of the. NET Framework, see Microsoft. NET Framework support Lifecycle Policy on the Microso FT Support website. Targeting and running apps for older versions
The. NET Framework versions 2.0, 3.0, and 3.5 is built with the same version of the CLR (CLR 2.0). These versions represent successive layers of a single installation. Each version was built incrementally on top of the earlier versions. It is not possible to run versions 2.0, 3.0, and 3.5 side by side on a computer. When you install version 3.5, your get the 2.0 and 3.0 layers automatically, and apps that were built for versions 2.0, 3.0 , and 3.5 can all run on version 3.5. 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 s Ingle Process. For more information, seeassemblies and side-by-side execution.
In addition, if your app targets version 2.0, 3.0, or 3.5, your users could be required to enable the. NET Framework 3.5 on A Windows 8 or Windows 8.1 computer before they can run your app. For more information, see Installing the. NET Framework 3.5 on Windows 8, Windows 8.1 and Windows 10. Next steps
If you're the new to the. NET Framework, see the overview for a introduction to key concepts and features.
For new features and improvements in the. NET Framework 4.5 and their point releases, see what ' s new.
For information about migrating your apps from the. NET Framework 4 to the. NET Framework 4.5 and their point releases, see T He migration Guide.
For information about determining which versions or updates is installed on a computer, see how to:determine which. NET The framework Versions is installed and how to:determine which. NET Framework Updates is installed.
See Also
Version compatibility in the. NET Framework
Microsoft. NET Framework Support Lifecycle Policy
Windows and. Net