Each version of .NET Framework contains the common language runtime (CLR), the base class libraries, and other managed libraries. This article describes the key features of .NET Framework by version, provides information about the underlying CLR versions and associated development environments, and identifies the versions that are installed by the Windows operating system (OS).
Each new version of .NET Framework adds new features but retains features from previous versions.
Note
.NET Framework is serviced independently from Windows updates with security and reliability bug fixes. In general, security updates are released quarterly. .NET Framework will continue to be included with Windows, with no plans to remove it. You don't need to migrate your .NET Framework apps, but for new development, use .NET instead of .NET Framework.
The CLR is identified by its own version number. The .NET Framework version number is incremented at each release, but the CLR version is not always incremented. For example, .NET Framework 4, 4.5, and later releases include CLR 4, but .NET Framework 2.0, 3.0, and 3.5 include CLR 2.0. (There was no version 3 of the CLR.)
Version informationThe tables that follow summarize .NET Framework version history and correlate each version with Visual Studio, Windows, and Windows Server. Visual Studio supports multi-targeting, so you're not limited to the version of .NET Framework that's listed.
Jump to:
To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
.NET Framework 4.8 Versions CLR 4 Windows âï¸ 11 October 2021 Release (Version 22000)To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
.NET Framework 4.7.2 Versions CLR 4 Included in Visual Studio 2019â Windows âï¸ 10 October 2018 Update (Version 1809)â Requires installing the .NET desktop development, ASP.NET and web development, Azure development, Office/SharePoint development, Mobile development with .NET, or .NET Core cross-platform development workloads.
To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
.NET Framework 4.7.1 Versions CLR 4 Windows âï¸ 10 Fall Creators Update (Version 1709)To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
.NET Framework 4.7 Versions CLR 4 Windows âï¸ 10 Creators Update (Version 1703)To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
.NET Framework 4.6.2 Versions CLR 4 Windows âï¸ 10 Anniversary Update (Version 1607)â 2012 R2
To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
.NET Framework 4.6.1 Versions CLR 4 Included in Visual Studio 20171 Windows âï¸ 10 November Update (Version 1511)1 Requires installing the .NET desktop development, ASP.NET and web development, Azure development, Office/SharePoint development, Mobile development with .NET, or .NET Core cross-platform development workloads.
To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
.NET Framework 4.6 Versions CLR 4 Included in Visual Studio 2015 Windows âï¸ 10â 8.1
To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
.NET Framework 4.5.2 Versions CLR 4 Windows â 8.1To determine the installed .NET version, use Release DWORD 379893. For more information, see instructions.
â 8
â 2012
To determine the installed .NET version, use the following Release DWORD:
For more information, see instructions.
Important
Starting with Visual Studio 2022, Visual Studio no longer includes .NET Framework components for .NET Framework 4.0 - 4.5.1 because these versions are no longer supported. Visual Studio 2022 and later versions can't build apps that target .NET Framework 4.0 through .NET Framework 4.5.1. To continue building these apps, you can use Visual Studio 2019 or an earlier version.
.NET Framework 4.5 Versions CLR 4 Included in Visual Studio 2012 Windows âï¸ 8To determine the installed .NET version, use Release DWORD 378389. For more information, see instructions.
Important
Starting with Visual Studio 2022, Visual Studio no longer includes .NET Framework components for .NET Framework 4.0 - 4.5.1 because these versions are no longer supported. Visual Studio 2022 and later versions can't build apps that target .NET Framework 4.0 through .NET Framework 4.5.1. To continue building these apps, you can use Visual Studio 2019 or an earlier version.
.NET Framework 4 Versions CLR 4 Included in Visual Studio 2010 Windows â 7To determine installed .NET version: See instructions.
Important
Starting with Visual Studio 2022, Visual Studio no longer includes .NET Framework components for .NET Framework 4.0 - 4.5.1 because these versions are no longer supported. Visual Studio 2022 and later versions can't build apps that target .NET Framework 4.0 through .NET Framework 4.5.1. To continue building these apps, you can use Visual Studio 2019 or an earlier version.
.NET Framework 3.5â Vista
Windows Server â Windows Server, version 1803*âï¸2008 R2 SP1*
â 2008 SP2
To determine installed .NET version: See instructions.
.NET Framework 3.0â 2003
To determine installed .NET version: See instructions.
.NET Framework 2.0To determine installed .NET version: See instructions.
.NET Framework 1.1To determine installed .NET version: See instructions.
.NET Framework 1.0 Versions CLR 1.0 Included in Visual Studio Visual Studio .NET Windows N/A Windows Server N/ATo determine installed .NET version: See instructions.
Note
.NET Framework 4.5 is an in-place update that replaces .NET Framework 4 on your computer, and similarly, .NET Framework 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, and 4.8 are in-place updates to .NET Framework 4.5. In-place update means that they use the same runtime version, but the assembly versions are updated and include new types and members. After you install one of these updates, your .NET Framework 4, .NET Framework 4.5, .NET Framework 4.6, or .NET Framework 4.7 apps should continue to run without requiring recompilation. However, the reverse is not true. We do not recommend running apps that target a later version of .NET Framework on an earlier version. For example, we do not recommend that you run an app the targets .NET Framework 4.6 on .NET Framework 4.5.
The following guidelines apply:
In Visual Studio, you can choose .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 executable. This assembly or executable can then be used on any computer that has .NET Framework 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, or 4.8 installed.
In Visual Studio, you can choose .NET Framework 4.5.1 as the target framework for a project to compile it as a .NET Framework 4.5.1 assembly or executable. Only run this assembly or executable on computers that have .NET Framework 4.5.1 or later installed. An executable that targets .NET Framework 4.5.1 will be blocked from running on a computer that only has an earlier version of .NET Framework, such as .NET Framework 4.5, installed. The user will be prompted to install .NET Framework 4.5.1. In addition, .NET Framework 4.5.1 assemblies should not be called from an app that targets an earlier version of .NET Framework, such as .NET Framework 4.5.
Note
.NET Framework 4.5.1 and .NET Framework 4.5 are used here only as examples. The principle described applies to any app that targets a later version of .NET Framework than the one installed on the system on which it's running.
Some changes in .NET Framework may require changes to your app code; see Application Compatibility before you run your existing apps with .NET Framework 4.5 or later versions. For more information about installing the current version, see Install the .NET Framework for developers. For information about support for the .NET Framework, see .NET Framework official support policy on the .NET website.
.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 versions. It's not possible to run versions 2.0, 3.0, and 3.5 side by side on a computer. When you install version 3.5, you 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, .NET Framework 4 ends this layering approach, and it and later releases (.NET Framework 4.5, 4.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, and 4.8) also represent successive layers of a single installation. Starting with .NET Framework 4, you can use in-process, side by side hosting to run multiple versions of the CLR in a single process. For more information, see Assemblies and Side-by-Side Execution.
In addition, if your app targets version 2.0, 3.0, or 3.5, your users may be required to enable .NET Framework 3.5 on a Windows 8, Windows 8.1, or Windows 10 computer before they can run your app. For more information, see Install the .NET Framework 3.5 on Windows 11, Windows 10, Windows 8.1, and Windows 8.
Important
Starting with Visual Studio 2022, Visual Studio no longer includes .NET Framework components for .NET Framework 4.0 - 4.5.1 because these versions are no longer supported. Visual Studio 2022 and later versions can't build apps that target .NET Framework 4.0 through .NET Framework 4.5.1. To continue building these apps, you can use Visual Studio 2019 or an earlier version.
Next stepsIf you're new to the .NET Framework, see the overview for an introduction to key concepts and features.
For new features and improvements in the .NET Framework 4.5 and its point releases, see What's new in the .NET Framework.
For information about migrating your app to a newer version of the .NET Framework, see the migration guide.
For information about determining which versions or updates are installed on a computer, see How to: Determine Which .NET Framework Versions Are Installed and How to: Determine Which .NET Framework Updates Are Installed.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4