Content deleted Content added
Tag: Reverted |
Added the original Microsoft .NET Logo |
||
| (13 intermediate revisions by 8 users not shown) | |||
Line 25:
FCL provides the [[user interface]], [[data access]], [[database connection|database connectivity]], [[cryptography]], [[web application]] development, numeric [[algorithm]]s, and [[computer networking|network communications]]. Programmers produce software by combining their [[source code]] with the .NET Framework and other libraries. The framework is intended to be used by most new applications created for the Windows platform. Microsoft also produces an [[integrated development environment]] for .NET software called [[Microsoft Visual Studio|Visual Studio]].
.NET Framework began as [[proprietary software]], although the firm worked to [[software standard|standardize]] the software stack almost immediately, even before its first release. Despite the standardization efforts, developers, mainly those in the [[free and open-source software]] communities, expressed their unease with the selected terms and the prospects of any free and open-source implementation, especially regarding [[software patent]]s. Since then, Microsoft has changed .NET development to more closely follow a contemporary model of a community-developed software project, including issuing an update to its patent promising to address the concerns.<ref name=":0">{{Cite web |date=November 19, 2014 |title=Microsoft gets on board with open source |url=https://opensource.com/business/14/11/microsoft-dot-net-empower-open-source-communities |access-date=2020-01-02 |website=Opensource.com |language=en |first1=Luis |last1=Ibanez |archive-date=January 2, 2020 |archive-url=https://web.archive.org/web/20200102202811/https://opensource.com/business/14/11/microsoft-dot-net-empower-open-source-communities |url-status=live }}</ref>
In April 2019, Microsoft released .NET Framework 4.8, the last major version of the framework as a proprietary offering, followed by .NET Framework 4.8.1 in August 2022. Only monthly security and reliability [[software bug|bug]] fixes to that version have been released since then. No further changes to that version are planned. The .NET Framework will continue to be included with future releases of Windows and continue to receive security updates, with no plans to remove it as of
==History==
Line 34:
In August 2000, [[Microsoft]] and [[Intel]] worked to standardize [[Common Language Infrastructure]] (CLI) and [[C Sharp (programming language)|C#]]. By December 2001, both were ratified [[Ecma International|by ECMA]] standards.<ref>{{cite web|url=http://www.ecma-international.org/publications/standards/Ecma-335.htm|title=Standard ECMA-335: Common Language Infrastructure (CLI)|date=June 2012|publisher=[[Ecma International|ECMA]]|edition=6|access-date=August 31, 2005|archive-date=June 29, 2013|archive-url=https://web.archive.org/web/20130629235609/http://www.ecma-international.org/publications/standards/Ecma-335.htm|url-status=dead}}</ref><ref name="Ecma-334">{{cite web|url=http://www.ecma-international.org/publications/standards/Ecma-334.htm|title=Standard ECMA-334: C# Language Specification|date=June 2006|publisher=[[Ecma International|ECMA]]|edition=4|access-date=August 31, 2005|archive-date=October 31, 2010|archive-url=https://web.archive.org/web/20101031042906/http://www.ecma-international.org/publications/standards/Ecma-334.htm|url-status=dead }}</ref> [[International Organization for Standardization]] (ISO) followed in April 2003. The current version of ISO standards are ISO/IEC 23271:2012 and ISO/IEC 23270:2006.<ref>{{cite web|url=http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=58046|title=ISO/IEC 23271:2012 Information technology – Common Language Infrastructure|publisher=[[International Organization for Standardization]]|date=February 13, 2012|edition=3|access-date=March 17, 2012|archive-date=March 17, 2012|archive-url=https://web.archive.org/web/20120317142950/http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=58046|url-status=live}}</ref><ref>{{cite web|url=http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=42926|title=ISO/IEC 23270:2006 – Information technology – Programming languages – C#|publisher=[[International Organization for Standardization]]|date=January 26, 2012 |edition=2|access-date=April 1, 2008|archive-date=December 6, 2010|archive-url=https://web.archive.org/web/20101206152217/http://www.iso.org/iso/iso_catalogue/catalogue_ics/catalogue_detail_ics.htm?csnumber=42926|url-status=live}}</ref>
[[File:Microsoft NET Logo.svg|thumb|The Original Microsoft .NET Logo]]
While Microsoft and their partners hold patents for CLI and C#, ECMA and ISO require that all patents essential to implementation be made available under "[[reasonable and non-discriminatory licensing|reasonable and non-discriminatory terms]]". The firms agreed to meet these terms, and to make the patents available royalty-free. However, this did not apply to the part of the .NET Framework not covered by ECMA-ISO standards, which included [[Windows Forms]], [[ADO.NET]], and [[ASP.NET]]. Patents that Microsoft holds in these areas may have deterred non-Microsoft implementations of the full framework.<ref>{{cite web|title=Microsoft's Empty Promise|url=http://www.fsf.org/news/2009-07-mscp-mono|work=[[Free Software Foundation]]|date=July 16, 2009 |first1=Brett |last1=Smith |quote=However, there are several libraries that are included with Mono, and commonly used by applications like Tomboy, that are not required by the standard. And just to be clear, we're not talking about Windows-specific libraries like ASP.NET and Windows Forms. Instead, we're talking about libraries under the System namespace that provide common functionality programmers expect in modern programming languages|access-date=August 3, 2009|archive-url=https://web.archive.org/web/20090819101829/http://www.fsf.org/news/2009-07-mscp-mono/|archive-date=August 19, 2009|url-status=live|df=dmy}}</ref>
Line 45:
[[File:Microsoft .NET Framework v4.5 logo.png|thumb|Microsoft .NET Framework v4.5 logo]]
In November 2014, Microsoft also produced an update to its patent grants, which further extends the scope beyond its prior pledges. Prior projects like [[Mono (software)|Mono]] existed in a legal [[loophole|
On March 31, 2016, Microsoft announced at [[Build (developer conference)|Microsoft Build]] that they will completely [[software relicensing|relicense]] Mono under an [[MIT License]] even in scenarios where formerly a commercial license was needed.<ref>{{cite web|last1=Krill|first1=Paul|title=Xamarin's Mono runtime gets a looser license|url=http://www.infoworld.com/article/3050732/microsoft-windows/xamarins-mono-runtime-gets-a-looser-license.html|website=[[InfoWorld]]|publisher=[[IDG]]|date=April 1, 2016|access-date=April 13, 2016|archive-date=April 16, 2016|archive-url=https://web.archive.org/web/20160416032759/http://www.infoworld.com/article/3050732/microsoft-windows/xamarins-mono-runtime-gets-a-looser-license.html|url-status=live}}</ref> Microsoft also supplemented its prior patent promise for Mono, stating that they will not assert any "applicable patents" against parties that are "using, selling, offering for sale, importing, or distributing Mono."<ref name=Ferraira1>{{cite web|url=http://techreport.com/news/29929/xamarin-now-comes-free-with-visual-studio|title=Xamarin now comes free with Visual Studio.|work=The Tech Report|date=March 31, 2016|first=Bruno|last=Ferraira|access-date=April 12, 2016|archive-date=April 2, 2016|archive-url=https://web.archive.org/web/20160402173444/http://techreport.com/news/29929/xamarin-now-comes-free-with-visual-studio|url-status=live}}</ref><ref name="Microsoft_PP_Mono">{{cite web|url=https://github.com/mono/mono/blob/master/PATENTS.TXT|title=Microsoft Patent Promise for Mono|work=Mono on GitHub |date=March 28, 2016|archive-url=https://web.archive.org/web/20160416133644/https://github.com/mono/mono/blob/master/PATENTS.TXT|archive-date=April 16, 2016|access-date=April 16, 2016|url-status=live|df=dmy}}</ref> It was announced that the Mono Project was contributed to the .NET Foundation. These developments followed the acquisition of [[Xamarin]], which began in February 2016 and was finished on March 18, 2016.<ref name="Friedman2">{{cite web|url=https://blog.xamarin.com/xamarin-for-all/|title=Xamarin for Everyone|work=Xamarin Blog |first1=Nat |last1=Friedman |date=March 31, 2016|archive-url=https://web.archive.org/web/20160412072728/https://blog.xamarin.com/xamarin-for-all/|archive-date=April 12, 2016|access-date=April 12, 2016}}</ref>
Microsoft's press release highlights that the cross-platform commitment now allows for a fully open-source, modern server-side .NET stack.<ref name=":0" /> Microsoft released the source code for WPF, Windows Forms and [[WinUI]] on December 4, 2018.<ref name="ms-wpf-winforms-oss">{{cite web|title=Announcing Open Source of WPF, Windows Forms, and WinUI at Microsoft Connect 2018|url=https://blogs.windows.com/buildingapps/2018/12/04/announcing-open-source-of-wpf-windows-forms-and-winui-at-microsoft-connect-2018/|website=Windows Developer Blog|date=December 4, 2018|publisher=Microsoft |first1=Kevin |last1=Gallo |access-date=December 24, 2018|archive-url=https://web.archive.org/web/20181215163944/https://blogs.windows.com/buildingapps/2018/12/04/announcing-open-source-of-wpf-windows-forms-and-winui-at-microsoft-connect-2018/|archive-date=December 15, 2018}}</ref>
==Architecture==
Line 65:
===Assemblies===
Compiled
A private key can also be used by the creator of the assembly for [[strong name|strong naming]]. The public key token determines the real-world identity of the assembly's signer. Only those knowing their private key (of the double-key cryptography system) can sign assemblies that have the same strong name as a prior version assembly. Strong naming is required to add assemblies to [[Global Assembly Cache]].
Line 73:
===Class library===
{{Main|Framework Class Library}}
.NET Framework includes an implementation of the CLI foundational [[Standard Libraries (CLI)|Standard Libraries]]. The .NET Framework Class Library (FCL) is organized in a hierarchy of [[namespace]]s. Most of the built-in [[application programming interface]]s (APIs) are part of either <code>System.*</code> or <code>Microsoft.*</code> namespaces. These class libraries implement many common functions, such as file reading and writing, graphic rendering, database interaction, and XML document manipulation. The class libraries are available for all [[List of CLI languages|CLI compliant languages]]. The FCL implements the CLI [[Base Class Library]] (BCL) and other class libraries—some are specified by CLI and
BCL includes a small subset of the entire class library and is the core set of classes that serve as the basic [[API]] of CLR.<ref name="bcllibs">{{cite web|url=https://msdn.microsoft.com/netframework/aa569603.aspx|title=Base Class Libraries Community |website=Microsoft |url-status=dead |archive-url=https://web.archive.org/web/20090424204812/http://msdn.microsoft.com/en-us/netframework/aa569603.aspx |archive-date=Apr 24, 2009 |access-date=June 1, 2008}}</ref> For .NET Framework most classes considered being part of BCL reside in <code>mscorlib.dll</code>, <code>System.dll</code> and <code>System.Core.dll</code>. BCL classes are available in .NET Framework as well as in CLI's alternative implementations, including [[.NET Compact Framework]], [[Microsoft Silverlight]], [[.NET Core]] and [[Mono (software)|Mono]].
FCL refers to the entire class library that ships with .NET Framework. It includes BCL, an expanded set of libraries, including [[Windows Forms]], [[ASP.NET]], and [[Windows Presentation Foundation]] (WPF), and also extensions to the base class libraries [[ADO.NET]], [[Language Integrated Query]] (LINQ), [[Windows Communication Foundation]] (WCF), and [[Workflow Foundation]] (WF). FCL is much larger in scope than standard libraries for languages like [[C++]], and comparable in scope to [[Java Class Library|standard libraries of Java]].
Line 105:
While Microsoft has never implemented the full framework on any system except Microsoft Windows, it has engineered the framework to be cross-platform,<ref>{{cite web|url=https://channel9.msdn.com/shows/Going+Deep/Scott-Guthrie-Silverlight-and-the-Cross-Platform-CLR|title=Scott Guthrie: Silverlight and the Cross-Platform CLR|date=April 30, 2007|publisher=[[Channel 9 (discussion forum)|Channel 9]]|access-date=April 16, 2016|archive-url=https://web.archive.org/web/20150522144655/http://channel9.msdn.com/shows/Going+Deep/Scott-Guthrie-Silverlight-and-the-Cross-Platform-CLR|archive-date=May 22, 2015|url-status=live|df=dmy}}</ref> and implementations are available for other operating systems (see [[Microsoft Silverlight|Silverlight]] and [[#Alternative implementations|§ Alternative implementations]]). Microsoft submitted the specifications for CLI (which includes the Base Class Libraries, CTS, and CIL),<ref>{{cite web|url=http://www.ecma-international.org/publications/standards/Ecma-335.htm|title=ECMA 335 – Standard ECMA-335 Common Language Infrastructure (CLI) 4th edition (June 2006)|date=June 1, 2006|access-date=June 1, 2008|publisher=ECMA|archive-url=https://web.archive.org/web/20080614092650/http://www.ecma-international.org/publications/standards/Ecma-335.htm|archive-date=June 14, 2008}}</ref><ref>{{cite web|url=http://standards.iso.org/ittf/PubliclyAvailableStandards/c042927_ISO_IEC_23271_2006(E)_Software.zip|title=ISO/IEC 23271:2006|publisher=ISO Standards |date=September 29, 2006|access-date=April 17, 2012|archive-date=July 1, 2018|archive-url=https://web.archive.org/web/20180701142510/http://standards.iso.org/ittf/PubliclyAvailableStandards/c042927_ISO_IEC_23271_2006%28E%29_Software.zip|url-status=dead }}</ref><ref>{{cite web|url=http://www.ecma-international.org/publications/techreports/E-TR-084.htm|title=Technical Report TR/84 Common Language Infrastructure (CLI) – Information Derived from Partition IV XML File|date=June 1, 2006|publisher=ECMA|access-date=April 16, 2016|archive-url=https://web.archive.org/web/20150307073541/http://www.ecma-international.org/publications/techreports/E-TR-084.htm|archive-date=March 7, 2015|url-status=dead|df=dmy}}</ref> [[C Sharp (programming language)|C#]],<ref name="Ecma-334"/> and C++/CLI<ref>{{cite web|url=http://www.ecma-international.org/publications/standards/Ecma-372.htm|title=Standard ECMA-372 C++/CLI Language Specification|date=December 1, 2005|publisher=ECMA|access-date=January 16, 2008|archive-url=https://web.archive.org/web/20080810165757/http://www.ecma-international.org/publications/standards/Ecma-372.htm|archive-date=August 10, 2008|url-status=dead}}</ref> to both [[Ecma International]] (ECMA) and [[International Organization for Standardization]] (ISO), making them available as official standards. This makes it possible for third parties to create compatible implementations of the framework and its languages on other platforms.
Core cross-platform .NET (formerly .NET Core) is officially available also for many Linux distributions and
===Security===
.NET Framework has its own security mechanism with two general features: [[Code Access Security]] (CAS), and validation and verification. CAS is based on evidence that is associated with a specific assembly. Typically, the evidence is the source of the assembly (whether it is installed on the local machine or has been downloaded from the Internet). CAS uses evidence to determine the permissions granted to the code. When calling code demands that it be granted a specific permission, CLR performs a call stack walk checking every assembly of each method in the call stack for the required permission; if any assembly is not granted the permission, it will throw a security exception.
[[Managed code|Managed]] [[Common Intermediate Language|CIL]] bytecode is easier to [[reverse engineering#Reverse engineering of software|reverse-engineer]] than native code, unless [[obfuscated code|obfuscated]].<ref>Gartner, Inc. as reported in "Hype Cycle for Cyberthreats, 2006", September 2006, Neil MacDonald; Amrit Williams, et al.</ref> {{Not a typo|.NET}} [[decompiler]] programs enable developers with no reverse-engineering skills to view the source code behind unobfuscated .NET assemblies. In contrast, apps compiled
===Memory management===
Line 194:
==References==
{{Reflist|30em}}
==External links==
| |||