This .NET Core is missing information about September 2015. Please expand the .NET Core to include this information. Further details may exist on the talk page.
Microsoft started development on the .NET Framework in the late 1990s originally under the name of Next Generation Windows Services (NGWS). By late 2000 the first beta versions of .NET 1.0 were released.[1] The first version of .NET Framework was released on 13 February 2002, bringing managed code to Windows NT 4.0, 98, 2000, ME and XP.
Since the first version, Microsoft has released nine more upgrades for .NET Framework, seven of which have been released along a new version of Visual Studio. Two of these upgrades, .NET Framework 2.0 and 4.0, have upgraded Common Language Runtime (CLR). New versions of .NET Framework replace older versions when the CLR version is the same.
a.^ .NET Framework 1.0 is an integral component of Windows XP Media Center Edition and Windows XP Tablet PC Edition. Installation CDs for the Home edition and the Professional edition of Windows XP SP1, SP2 or SP3 come with .NET Framework 1.0 installation packages.[4]
b.^ Installation CDs for the Home edition and the Professional edition of Windows XP SP2 and SP3 come with .NET Framework 1.1 installation packages.[4]
c.^ .NET Framework is not automatically installed with this operating system. It must be installed either from a Windows installation media or from the Internet on demand. Control Panel or Server Manager always attempts the latter.[30]
d.^ This date applies only when running on Windows 10 version 1809, Windows Server 2019 or later. On older versions of Windows, .NET Framework 3.5 Service Pack 1 adopts the lifecycle of the underlying Windows operating system.[11]
The first version of the .NET Framework was released on 13 February 2002 for Windows 98, ME, NT 4.0, 2000, and XP. Mainstream support for this version ended on 10 July 2007, and extended support ended on 14 July 2009, with the exception of Windows XP Media Center and Tablet PC editions.[11]
.NET Framework 1.1
Version 1.1 is the first minor .NET Framework upgrade. It is available on its own as a redistributable package or in a software development kit, and was published on 3 April 2003. It is also part of the second release of Visual Studio .NET 2003. This is the first version of the .NET Framework to be included as part of the Windows operating system, shipping with Windows Server 2003. Mainstream support for .NET Framework 1.1 ended on 14 October 2008, and extended support ended on 8 October 2013. Since version 1.1 is a component of Windows Server 2003, it will receive extended support along with the OS until 14 July 2015. .NET Framework 1.1 is the last version to support Windows NT 4.0.
Installing .NET Framework 1.1 also provides the system support for version 1.0, except in rare instances where an application will not run because it checks the version number of a library.[31]
Changes in 1.1 include:
Built-in support for mobile ASP.NET controls, which was previously available as an add-on
Enables Windows Forms assemblies to execute in a semi-trusted manner from the Internet
.NET Framework 2.0 with Service Pack 2 requires Windows 2000 with SP4 plus KB835732 or KB891861 update, Windows XP with SP2 plus Windows Installer 3.1. It is the last version to support for Windows 2000 although there have been some unofficial workarounds to use a subset of the functionality from Version 3.5 in Windows 2000.[34]
A new hosting API for native applications wishing to host an instance of the .NET runtime: The new API gives a fine grain control on the behavior of the runtime with regards to multithreading, memory allocation and assembly loading. It was initially developed to efficiently host the runtime in Microsoft SQL Server, which implements its own scheduler and memory manager.
Many additional and improved ASP.NET web controls[which?]
New data controls[which?] with declarative data binding
New personalization features for ASP.NET, such as support for themes, skins, master pages and webparts
Language support for generics built directly into the .NET CLR
.NET Framework 3.0
.NET Framework 3.0, formerly called WinFX,[35] was released on 21 November 2006. It includes a new set of managed code APIs that are an integral part of Windows Vista and Windows Server 2008. It is also available for Windows XP SP2 and Windows Server 2003 as a download. There are no major architectural changes included with this release; .NET Framework 3.0 uses the same CLR as .NET Framework 2.0.[36] 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:
Windows Communication Foundation (WCF), formerly code-named Indigo: A service-oriented messaging system which allows programs to interoperate locally or remotely similar to web services
Windows CardSpace, formerly code-named InfoCard: A software component which securely stores a person's digital identities and provides a unified interface for choosing the identity for a particular transaction, such as logging in to a website
.NET Framework 3.5
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 as Language Integrated Query (LINQ). These changes do not affect applications written for version 2.0, however.[38]
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 and Windows Embedded CE devices.
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,[40] especially with WPF where 20–45% improvements are expected. Two new data service components have been added, the ADO.NET Entity Framework and ADO.NET Data Services. Two new assemblies for web development, System.Web.Abstraction and System.Web.Routing, have been added; these are used in the ASP.NET MVC Framework and, reportedly, will be used in the future release of ASP.NET Forms applications. Service Pack 1 is included with SQL Server 2008 and Visual 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).
.NET Framework 3.5 SP1 Client Profile
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 to desktop applications.[41] 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 using Windows Update. When using the off-line installer or any other OS, the download size is still 250 MB.[42]
Microsoft announced the intention to ship .NET Framework 4 on 29 September 2008. The Public Beta was released on 20 May 2009.[46]
On 28 July 2009, a second release of the .NET Framework 4 beta was made available with experimental software transactional memory support.[47] 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.[48] At the same time, Microsoft announced the expected launch date for .NET Framework 4 as 22 March 2010.[48] This launch date was subsequently delayed to 12 April 2010.[49]
On 18 April 2011, version 4.0.1 was released supporting some customer-demanded fixes for Windows Workflow Foundation.[51] Its design-time component, which requires Visual Studio 2010 SP1, adds a workflow state machine designer.[52]
On 19 October 2011, version 4.0.2 was released supporting some new features of Microsoft SQL Server.[53]
After the release of the .NET Framework 4, Microsoft released a set of enhancements, named Windows Server AppFabric,[55] for application server capabilities in the form of AppFabric Hosting[56][57] and in-memory distributed caching support.
.NET Framework 4.5
.NET Framework 4.5 was released on 15 August 2012;[58] a set of new or improved features were added into this version.[59] The .NET Framework 4.5 is only supported on Windows Vista or later.[60][61] The .NET Framework 4.5 uses Common Language Runtime 4.0, with some additional runtime features.[62]
.NET for Metro style-apps
Metro-style apps were originally designed for specific form factors and leverage the power of the Windows operating system. A subset of the .NET Framework is available for building Metro-style apps for Windows 8 and later using C# or Visual Basic. This subset is called .NET APIs for apps. This version of .NET Framework, as well as the runtime and libraries used for Metro-style apps, is a part of Windows 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++ and HTML5 with JavaScript.
Core Features
Ability to limit how long the regular expression engine will attempt to resolve a regular expression before it times out.
Support for versioning of cultural string ordering and comparison data.
Better performance when retrieving resources.
Zip compression improvements to reduce the size of a compressed file.
Ability to customize a reflection context to override default reflection behavior through the CustomReflectionContext class.
New asynchronous features were added to the C# and Visual Basic languages. These features add a task-based model for performing asynchronous operations,[63][64] implementing futures and promises.
Managed Extensibility Framework (MEF)
This section needs expansion. You can help by adding to it. (January 2015)
Support for model binders in Web Forms. These let you bind data controls directly to data-access methods, and automatically convert user input to and from .NET Frameworkdata types.
Support for unobtrusive JavaScript in client-side validation scripts.
Improved handling of client script through bundling and minification for improved page performance.
Integrated encoding routines from the AntiXSS library (previously an external library) to protect from cross-site scripting attacks.
The release of .NET Framework 4.5.2 was announced on 5 May 2014.[67] For Windows Forms applications, improvements were made for high DPI 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.[67]
.NET Framework 4.6
.NET Framework 4.6 was announced on 12 November 2014.[68] It was released on 20 July 2015.[69] It supports a new just-in-time compiler (JIT) for 64-bit systems called RyuJIT, which features higher performance and support for SSE2 and AVX2 instruction sets. WPF and Windows Forms both have received updates for high DPI scenarios. Support for TLS 1.1 and TLS 1.2 has been added to WCF.[69]
^ abcdefghijklmno"Microsoft .NET Framework". Microsoft. Retrieved 14 January 2023. Cite error: The named reference "MS_DotNET_EoL" was defined multiple times with different content (see the help page).
^"STM.NET on DevLabs". 27 July 2008. Archived from the original on 10 August 2009. Retrieved 6 August 2008. ((cite web)): Unknown parameter |deadurl= ignored (|url-status= suggested) (help)
