 | This article mayrequirecleanup to meet Wikipedia'squality standards. The specific problem is:Needs cleanup per NOTCHANGELOG. Please helpimprove this article if you can.(December 2023) (Learn how and when to remove this message) |
Microsoft started development on the.NET Framework in the late 1990s originally under the name of Next Generation Windows Services (NGWS). By late 2001 the first beta versions of .NET Framework 1.0 were released.[1] The first version of .NET Framework was released on 13 February 2002, bringingmanaged code toWindows NT 4.0,98,2000,ME andXP.
Since its initial release, Microsoft has issued nine subsequent upgrades to the .NET Framework, with seven coinciding with new releases ofVisual Studio. Notably, versions 2.0 and 4.0 introduced significant updates toCommon Language Runtime (CLR), enhancing performance, security, and language interoperability. In cases where the CLR version remains unchanged, newer framework releases typically replace previous ones through in-place updates.
The .NET Framework family also includes two versions formobile orembedded device use. A reduced version of the framework, the.NET Compact Framework, is available onWindows CE platforms, includingWindows Mobile devices such assmartphones. Additionally, the.NET Micro Framework is targeted at severely resource-constrained devices.
.NET Framework 4.8 was announced as the last major version of .NET Framework, with future work going into the rewritten andcross-platform.NET Core platform (later, simply.NET), which shipped as.NET 5 in November 2020.[2][3] However, .NET Framework 4.8.1 was released in August 2022.[4]
| Version | CLR | Release date | Support ended[9][10] | Visual Studio | Included in | Can be installed on | Replaces | ||
|---|---|---|---|---|---|---|---|---|---|
| Windows | Windows Server | Windows | Windows Server | ||||||
| 1.0 | 1.0 | 2002-01-15[11][12] | Visual Studio .NET (2002) | — | — | NT 4.0 SP6a,98,98SE,Me,2000,XP | NT 4.0 SP6a, 2000, 2003 | — | |
| 1.0 SP1 | ↑ | 2002-03-19[13] | — | — | ↑ | ↑ | ↑ | ||
| 1.0 SP2 | ↑ | 2002-08-07[14] | XP SP1[a] | — | ↑ | ↑ | ↑ | ||
| 1.0 SP3 | ↑ | 2004-08-30[15] | 2009-07-14 | — | — | ↑ | ↑ | ↑ | |
| 1.1 | 1.1 | 2003-04-09[16] | Visual Studio .NET 2003 | — | 2003 (x86) | NT 4.0 SP6a, 98, 98SE, Me, 2000, XP, Vista | NT 4.0 SP6a, 2000, 2003 (x64), 2008 | 1.0[17] | |
| 1.1 SP1 | ↑ | 2004-08-30[15] | 2013-10-08 | XP SP2, SP3[b] | 2003 SP1, SP2 (x86) | ↑ | ↑ | ↑ | |
| 2.0 | 2.0 | 2005-10-27[18] | Visual Studio 2005 | — | 2003 R2 | 98, 98SE, Me, 2000 SP3, XP SP2 | 2000 SP3, 2003 | — | |
| 2.0 SP1 | ↑ | 2007-11-19[19] | — | 2008 | 2000 SP4, XP SP2 | 2000 SP4, 2003 SP1 | ↑ | ||
| 2.0 SP2 | ↑ | 2008-08-11[20] | 2011-07-12 | — | 2008 SP2,2008 R2 | ↑ | ↑ | ↑ | |
| 3.0 | 2.0 | 2006-11-06[21] | Visual Studio 2008 | Vista | — | XP SP2 | 2003 SP1 | 2.0 | |
| 3.0 SP1 | ↑ | 2007-11-19[19] | Vista SP1 | 2008[c] | ↑ | ↑ | ↑ | ||
| 3.0 SP2 | ↑ | 2008-08-11[20] | 2011-07-12 | Vista SP2 | 2008 SP2,[c] 2008 R2[c] | ↑ | ↑ | ↑ | |
| 3.5 | 2.0 | 2007-11-19[19] | Visual Studio 2008 | — | — | XP SP2, Vista | 2003 SP1, 2008 | 2.0, 3.0 | |
| 3.5 SP1 | ↑ | 2008-08-11[20] | 2029-01-09[d] | Visual Studio 2008 SP1 | 7,8,[c]8.1,[c]10,[c]11[c] | 2008 R2,[c]2012,[c]2012 R2,[c] v1709-v20H2,[c]2016-2022,[c] v23H2,[c]2025[c] | ↑ | ↑ | ↑ |
| 4.0 | 4 | 2010-04-12[22] | 2016-01-12 | Visual Studio 2010 | — | — | XP SP3, Vista SP1, 7 | 2003 SP2, 2008, 2008 R2 | — |
| 4.5 | 4 | 2012-08-15[23] | 2016-01-12 | Visual Studio 2012 | 8 | 2012 | Vista SP2, 7 SP1 | 2008 SP2, 2008 R2 SP1 | 4.0 |
| 4.5.1 | 4 | 2013-10-17[24] | 2016-01-12 | Visual Studio 2013 | 8.1 | 2012 R2 | Vista SP2, 7 SP1, 8 | 2008 SP2, 2008 R2 SP1, 2012 | 4.0, 4.5 |
| 4.5.2 | 4 | 2014-05-05[25] | 2022-04-26 | Visual Studio 2015 | — | — | Vista SP2, 7 SP1, 8, 8.1 | 2008 SP2, 2008 R2 SP1, 2012, 2012 R2 | 4.0-4.5.1 |
| 4.6 | 4 | 2015-07-20[26] | 2022-04-26 | Visual Studio 2015 | 10 v1507 | — | Vista SP2, 7 SP1, 8, 8.1 Update | 2008 SP2, 2008 R2 SP1, 2012, 2012 R2 Update | 4.0-4.5.2 |
| 4.6.1 | 4 | 2015-11-30[27] | 2022-04-26 | Visual Studio 2015 Update 1 | 10 v1511 | — | 7 SP1, 8, 8.1 Update, 10 v1507 | 2008 R2 SP1, 2012, 2012 R2 Update | 4.0-4.6 |
| 4.6.2 | 4 | 2016-08-02[28] | 2027-01-12 | Visual Studio 2017 15.0 | 10 v1607 | 2016 | 7 SP1, 8.1 Update, 10 v1507-v1511 | 2008 R2 SP1, 2012, 2012 R2 Update | 4.0-4.6.1 |
| 4.7 | 4 | 2017-04-05[29] | Same as parent OS | Visual Studio 2017 15.1 | 10 v1703 | — | 7 SP1, 8.1 Update, 10 v1607 | 2008 R2 SP1, 2012, 2012 R2 Update, 2016 | 4.0-4.6.2 |
| 4.7.1 | 4 | 2017-10-17[30] | Visual Studio 2017 15.5 | 10 v1709 | v1709 | 7 SP1, 8.1 Update, 10 v1607-v1703 | 2008 R2 SP1, 2012, 2012 R2 Update, 2016 | 4.0-4.7 | |
| 4.7.2 | 4 | 2018-04-30[31] | Visual Studio 2017 15.8 | 10 v1803-v1809 | v1803-v1809,2019 | 7 SP1, 8.1 Update, 10 v1607-v1709 | 2008 R2 SP1, 2012, 2012 R2 Update, 2016, v1709 | 4.0-4.7.1 | |
| 4.8 | 4 | 2019-04-18[32] | Visual Studio 2019 16.3 | 10 v1903-v22H2,11 v21H2 | v1903-v20H2,2022 | 7 SP1, 8.1 Update, 10 v1607-v1809 | 2008 R2 SP1, 2012, 2012 R2 Update, 2016, v1803-v1809, 2019 | 4.0-4.7.2 | |
| 4.8.1 | 4 | 2022-08-09[33] | Visual Studio 2022 17.3 | 11 v22H2-v25H2 | v23H2,2025 | 10 v20H2-v22H2, 11 v21H2 | 2022 | 4.0-4.8 | |
Notes:
The first version of the .NET Framework was released on 15 January 2002 forWindows 98,ME,NT 4.0,2000, andXP. Mainstream support for this version ended on 10 July 2007, and extended support ended on 14 July 2009, with the exception ofWindows XP Media Center andTablet PC editions.[10]
On 19 June 2001, the tenth anniversary of the release of Visual Basic, .NET Framework 1.0 Beta 2 was released.[35]
.NET Framework 1.0 is supported onWindows 98,ME,NT 4.0 (with Service Pack 6a),2000,XP, andServer 2003. Applications utilizing .NET Framework 1.0 will also run on computers with .NET Framework 1.1 installed, which supports additional operating systems.[36]
The .NET Framework 1.0 Service Pack 1 was released on 19 March 2002.[37]
.NET Framework 1.0 Service Pack 2 was released on 7 August 2002.[38]
.NET Framework 1.0 Service Pack 3 was released on 30 August 2004.[39]
Version 1.1 is the first minor .NET Framework upgrade. It is available on its own as aredistributable package or in asoftware development kit, and was published on 3 April 2003. It is also part of the second release ofVisual Studio .NET 2003. This is the first version of the .NET Framework to be included as part of the Windows operating system, shipping withWindows Server 2003. Mainstream support for .NET Framework 1.1 ended on 14 October 2008, and extended support ended on 8 October 2013. .NET Framework 1.1 provides fullbackward compatibility to version 1.0, except in rare instances where an application will not run because it checks the version number of a library.[40]
Changes in 1.1 include:[41]
.NET Framework 1.1 is supported onWindows 98,ME,NT 4.0 (with Service Pack 6a),2000,XP,Server 2003,Vista, andServer 2008.[36][42]
The .NET Framework 1.1 Service Pack 1 was released on 30 August 2004.[43] It requiresWindows NT 4.0 SP6a plusWindows Installer 2.0. It is the last version to supportWindows NT 4.0 SP6a,Windows 2000 RTM–SP2 andWindows XP RTM–SP1.
Version 2.0 was released on 27 October 2005. It was also released along withVisual Studio 2005,Microsoft SQL Server 2005, andBizTalk 2006. A software development kit for this version was released on 29 November 2006.[44] Support ended on 12 July 2011. It is the last version to supportWindows 98,Windows 2000 SP3,Windows ME andWindows Server 2003 RTM.[45]
Changes in 2.0 include:
.NET Framework 2.0 is supported onWindows 98,ME,2000 (with Service Pack 3 or higher),XP (with Service Pack 2 or higher),Server 2003,Server 2008 andServer 2008 R2.[6] Applications utilizing .NET Framework 2.0 will also run on computers with .NET Framework 3.0 or 3.5 installed, which supports additional operating systems.
The .NET Framework 2.0 Service Pack 1 was released on 19 November 2007.[46] It requires Windows 2000 with SP4.
The .NET Framework 2.0 Service Pack 2 was released on 11 August 2008.[47] It requires Windows 2000 with SP4 plus KB835732 or KB891861 update,Windows XP with SP2 plusWindows Installer 3.1. It is the last version to supportWindows 2000 SP4 although there have been some unofficial workarounds to use a subset of the functionality from Version 3.5 in Windows 2000.[48]
.NET Framework 3.0, formerly called WinFX,[49] was released on 6 November 2006. It includes a new set ofmanaged code APIs that are an integral part ofWindows Vista andWindows Server 2008. It is also available forWindows XP SP2 andWindows Server 2003 as a download. There are no major architectural changes included with this release; .NET Framework 3.0 uses the sameCLR as .NET Framework 2.0.[50] Unlike the previous major .NET releases there was no .NET Compact Framework release made as a counterpart of this version. Version 3.0 of the .NET Framework shipped with Windows Vista. It also shipped with Windows Server 2008 as an optional component (disabled by default).
.NET Framework 3.0 consists of four major new components:
.NET Framework 3.0 is supported onWindows XP,Server 2003,Vista,Server 2008, andServer 2008 R2.[6] Applications utilizing .NET Framework 3.0 will also run on computers with .NET Framework 3.5 installed, which supports additional operating systems.
.NET Framework 3.0 Service Pack 1 was released on 19 November 2007.[52]
.NET Framework 3.0 Service Pack 2 was released on 11 August 2008.[53]
Version 3.5 of the .NET Framework was released on 19 November 2007. As with .NET Framework 3.0, version 3.5 uses Common Language Runtime (CLR) 2.0, that is, the same version as .NET Framework version 2.0. In addition, .NET Framework 3.5 also installs .NET Framework 2.0 SP1 and 3.0 SP1 (with the later 3.5 SP1 instead installing 2.0 SP2 and 3.0 SP2), which adds some methods and properties to the BCL classes in version 2.0 which are required for version 3.5 features such asLanguage Integrated Query (LINQ). These changes do not affect applications written for version 2.0, however.[54]
As with previous versions, a new .NET Compact Framework 3.5 was released in tandem with this update in order to provide support for additional features on Windows Mobile andWindows Embedded CE devices.
The source code of theFramework Class Library in this version has been partially released (for debugging reference only) under theMicrosoft Reference Source License.[55]
.NET Framework 3.5 is supported onWindows XP (with Service Pack 2 or higher),Server 2003 (with Service Pack 1 or higher),Vista,Server 2008,7,Server 2008 R2,8,Server 2012,8.1,Server 2012 R2,10, andServer 2016.[6] Starting from Windows 8, .NET Framework 3.5 is an optional feature that can be turned on or off in control panel.
.NET Framework 3.5 is also available as a WindowsContainer image, allowing old applications that rely on .NET Framework 2.0–3.5 to run in acontainer environment.[56]
The .NET Framework 3.5 Service Pack 1 was released on 11 August 2008. This release adds new functionality and provides performance improvements under certain conditions,[57] especially with WPF where 20–45% improvements are expected. Two new data service components have been added, theADO.NET Entity Framework andADO.NET Data Services. Two new assemblies for web development, System.Web.Abstraction and System.Web.Routing, have been added; these are used in theASP.NET MVC framework and, reportedly, will be used in the future release of ASP.NET Forms applications. Service Pack 1 is included withSQL Server 2008 andVisual Studio 2008 Service Pack 1. It also featured a new set of controls called "Visual Basic Power Packs" which brought back Visual Basic controls such as "Line" and "Shape." Version 3.5 SP1 of the .NET Framework shipped with Windows 7. It also shipped with Windows Server 2008 R2 as an optional component (disabled by default). It is the last version to supportWindows XP SP2,Windows Server 2003 SP1 andWindows Vista RTM.
For the .NET Framework 3.5 SP1 there is also a new variant of the .NET Framework, called the ".NET Framework Client Profile", which at 28 MB is significantly smaller than the full framework and only installs components that are the most relevant todesktop applications.[58] However, the Client Profile amounts to this size only if using the online installer on Windows XP SP2 when no other .NET Frameworks are installed or usingWindows Update. When using the off-line installer or any other OS, the download size is still 250 MB.[59]
Key focuses for this release are:
.NET Framework 4.0 is supported onWindows XP (with Service Pack 3),Windows Server 2003 (with Service Pack 2),Vista (with Service Pack 1 or higher),Server 2008,7 andServer 2008 R2.[6] Applications utilizing .NET Framework 4.0 will also run on computers with .NET Framework 4.5 or 4.6 installed, which supports additional operating systems. Support for .NET Framework 4.0 ended on 12 April 2016 and is no longer providing technical support, bug fixes, or security fixes for .NET Framework 4.0 vulnerabilities which may be subsequently reported or discovered. It is the last version to supportWindows XP SP3,Windows Server 2003 SP2,Windows Vista SP1,Windows Server 2008 RTM,Windows 7 RTM andWindows Server 2008 R2 RTM.
Microsoft announced the intention to ship .NET Framework 4 on 29 September 2008. The Public Beta was released on 20 May 2009.[66]
On 28 July 2009, a second release of the .NET Framework 4 beta was made available with experimentalsoftware transactional memory support.[67] This functionality is not available in the final version of the framework.
On 19 October 2009, Microsoft released Beta 2 of the .NET Framework 4.[68] At the same time, Microsoft announced the expected launch date for .NET Framework 4 as 22 March 2010.[68] This launch date was subsequently delayed to 12 April 2010.[69]
On 10 February 2010, arelease candidate was published.[70]
On 12 April 2010, the final version of .NET Framework 4.0 was launched alongside the final release ofMicrosoft Visual Studio 2010.[71]
On 18 April 2011, version 4.0.1 was released supporting some customer-demanded fixes forWindows Workflow Foundation.[72][73] Its design-time component, which requires Visual Studio 2010 SP1, adds a workflow state machine designer.
On 27 October 2011, version 4.0.2 was released supporting some new features ofMicrosoft SQL Server.[74][75]
On 5 March 2012, version 4.0.3 was released.[76][77]
After the release of the .NET Framework 4, Microsoft released a set of enhancements, named Windows Server AppFabric,[78] forapplication server capabilities in the form of AppFabric Hosting[79][80] and in-memory distributed caching support.
.NET Framework 4.5 was released on 15 August 2012;[81] a set of new or improved features were added into this version.[82] NET Framework 4.5 is supported onWindows Vista or later.[83][84] The .NET Framework 4.5 uses Common Language Runtime 4.0, with some additional runtime features.[85]
.NET Framework 4.5 is supported onWindows Vista (with Service Pack 2),Server 2008 (with Service Pack 2),7 (with Service Pack 1),Server 2008 R2 (with Service Pack 1),8,Server 2012,8.1 andServer 2012 R2.[6] Applications utilizing .NET Framework 4.5 will also run on computers with .NET Framework 4.6 installed, which supports additional operating systems.
Metro-style apps were originally designed for specific form factors and leverage the power of the Windows operating system. Two subset of the .NET Framework is available for building Metro-style apps usingC# orVisual Basic: One forWindows 8 andWindows 8.1, called.NET APIs for Windows 8.x Store apps. Another forUniversal Windows Platform (UWP), called.NET APIs for UWP. This version of .NET Framework, as well as the runtime and libraries used for Metro-style apps, is a part ofWindows Runtime, the new platform and development model for Metro-style apps. It is an ecosystem that houses many platforms and languages, including.NET Framework,C++ andHTML5 withJavaScript.[86]
The Managed Extensibility Framework or MEF is a library for creating lightweight, extensible applications. It allows application developers to discover and use extensions with no configuration required. It also lets extension developers easily encapsulate code and avoid fragile hard dependencies. MEF not only allows extensions to be reused within applications, but across applications as well.[89]
The release of .NET Framework 4.5.1 was announced on 17 October 2013 along Visual Studio 2013.[90] This version requiresWindows Vista SP2 and later[91] and is included withWindows 8.1 andWindows Server 2012 R2. New features of .NET Framework 4.5.1:[92]
The release of .NET Framework 4.5.2 was announced on 5 May 2014.[93] This version requiresWindows Vista SP2 and later.[94] ForWindows Forms applications, improvements were made for highDPI scenarios. For ASP.NET, higher reliability HTTP header inspection and modification methods are available as is a new way to schedule background asynchronous worker tasks.[93]
.NET Framework 4.6 was announced on 12 November 2014.[95] It was released on 20 July 2015.[96] It supports a newjust-in-time compiler (JIT) for 64-bit systems called RyuJIT, which features higher performance and support forSSE2 andAVX2 instruction sets. WPF and Windows Forms both have received updates for high DPI scenarios. Support forTLS 1.1 and TLS 1.2 has been added to WCF.[96] This version requiresWindows Vista SP2 or later.[97] It is the last version to supportWindows Vista SP2 andWindows Server 2008 SP2.
The cryptographic API in .NET Framework 4.6 uses the latest version ofWindows CNG cryptography API. As a result,NSA Suite B Cryptography is available to .NET Framework. Suite B consists ofAES, theSHA-2 family of hashing algorithms,elliptic curve Diffie–Hellman, andelliptic curve DSA.[96][98]
.NET Framework 4.6 is supported onWindows Vista (with Service Pack 2),Server 2008 (with Service Pack 2),7 (with Service Pack 1),Server 2008 R2 (with Service Pack 1),8,Server 2012,8.1,Server 2012 R2,10 andServer 2016.[6] Support for .NET Framework 4.6 ended on 26 April 2022.
The release of .NET Framework 4.6.1 was announced on 30 November 2015.[99] This version requiresWindows 7 SP1 or later. It is the last version to supportWindows 8.[97] New features and APIs include:
The preview of .NET Framework 4.6.2 was announced on 30 March 2016.[100] It was released on 2 August 2016.[101] This version requiresWindows 7 SP1 or later. It is the last version to supportWindows 10 (RTM–v1511).[97] New features include:
.NET Framework 4.6.2 is also shipped as Windows container image.
On 5 April 2017, Microsoft announced that .NET Framework 4.7 was integrated intoWindows 10 Creators Update, promising a standalone installer for other Windows versions. An update forVisual Studio 2017 was released on this date to add support for targeting .NET Framework 4.7.[102] The promised standalone installer for Windows 7 and later was released on 2 May 2017,[103] but it had prerequisites not included with the package.[104] NET Framework 4.7 dropped support forWindows 8 and will only run on Windows 7 Service Pack 1 and later.
New features in .NET Framework 4.7 include:[105]
.NET Framework 4.7 is supported onWindows 7 (with Service Pack 1),Server 2008 R2 (with Service Pack 1),Server 2012,8.1,Server 2012 R2,10,Server 2016 andServer 2019.[6]
.NET Framework 4.7 is also shipped as a Windows container image.
.NET Framework 4.7.1 was released on 17 October 2017.[106] Amongst the fixes and new features, it corrects a d3dcompiler dependency issue.[107] It also adds compatibility with the .NET Standard 2.0 out of the box.[108]
.NET Framework 4.7.1 is also shipped as a Windows container image.
.NET Framework 4.7.2 was released on 30 April 2018.[109] Amongst the changes are improvements to ASP.NET, BCL, CLR, ClickOnce, Networking, SQL, WCF, Windows Forms, Workflow and WPF.[110] This version is included withServer 2019.[6]
.NET Framework 4.7.2 is also shipped as a Windows container image.
.NET Framework 4.8 was released on 18 April 2019.[111][112] It was the final version of .NET Framework released afterWindows Vista reachedend of life on 11 April 2017, with future work going into the.NET Core platform that eventually became .NET 5 and onwards.[2] This release includedJIT enhancements ported from .NET Core 2.1,High DPI enhancements for WPF applications, accessibility improvements, performance updates, and security enhancements.[113] Over five months after its release, an update for Visual Studio 2019 was released on 23 September 2019 to add support for targeting .NET Framework 4.8. It supportedWindows 7 (with Service Pack 1),Server 2008 R2 (with Service Pack 1),Server 2012,8.1,Server 2012 R2,10,Server 2016 andServer 2019[6] and also shipped as a Windows container image. It is the last version to supportWindows 7 SP1,Windows Server 2008 R2 SP1,Windows Server 2012,Windows 8.1,Windows Server 2012 R2,Windows 10 (v1607–1809),Windows Server 2016, Windows Server (v1709–1809) andWindows Server 2019, although it is only supported as included in Windows 10 (v1903–2004) and Windows Server (v1903–2004).
The most-recent release is 4.8.0 Build 4115, with an offline installer size of 115 MB (121,307,088 bytes) and a digital signature date of May 1, 2021.
.NET Framework 4.8.1 was released on 9 August 2022.[4] This version includes the nativeARM64 support, WCAG2.1 compliant accessible tooltips, and accessibility improvements for Windows Forms. It is supported onWindows 10 (v20H2–22H2), Windows Server (v20H2),Windows Server 2022 andWindows 11.
The most-recent release is 4.8.1 Build 9195, with an offline installer size of 74 MB (77,668,504 bytes) and a digital signature date of September 28, 2023.
The team is updating the System.Security.Cryptography APIs to support the Windows CNG cryptography APIs [...] since it supports modern cryptography algorithms [Suite B Support], which are important for certain categories of apps.
