The .NET Framework is a software framework developed by Microsoft that runs primarily on Windows. It includes a large class library and provides language interoperability across programming languages. Programs written for .NET execute in the Common Language Runtime (CLR), which provides services like security and memory management. The .NET Framework includes versions for mobile devices and supports multiple programming languages that compile to an intermediate language and are then compiled to native code when executing.

1. .NET Framework
".NET” redirects here. For the top-level Internet domain,
see .net. For other uses, see .NET (disambiguation).
.NET Framework (pronounced dot net) is a software
framework developed by Microsoft that runs primarily
on Microsoft Windows. It includes a large class library
known as Framework Class Library (FCL) and provides
language interoperability (each language can use code
written in other languages) across several programming
languages. Programs written for .NET Framework exe-
cute in a software environment (as contrasted to hardware
environment), known as Common Language Runtime
(CLR), an application virtual machine that provides
services such as security, memory management, and
exception handling. FCL and CLR together constitute
.NET Framework.
FCL provides user interface, data access, database con-
nectivity, cryptography, web application development,
numeric algorithms, and network communications. Pro-
grammers produce software by combining their own
source code with .NET Framework and other libraries.
.NET Framework is intended to be used by most new ap-
plications created for the Windows platform. Microsoft
also produces an integrated development environment
largely for .NET software called Visual Studio.
.NET Framework started out as a proprietary framework,
although the company worked to standardize the soft-
ware stack almost immediately, even before its first re-
lease. Despite the standardization efforts, developers—
particularly those in the free and open-source software
communities—expressed their uneasiness with the se-
lected terms and the prospects of any free and open-
source implementation, especially with regard to software
patents. Since then, Microsoft has changed .NET devel-
opment to more closely follow a contemporary model of
a community-developed software project, including issu-
ing an update to its patent that promises to address the
concerns.
.NET Framework family also includes two versions for
mobile or embedded device use. A reduced version of
the framework, .NET Compact Framework, is available
on Windows CE platforms, including Windows Mobile
devices such as smartphones. Additionally, .NET Micro
Framework is targeted at severely resource-constrained
devices.
1 History
Main article: .NET Framework version history
Microsoft started development of .NET Framework in
the late 1990s, originally under the name of Next Gener-
ation Windows Services (NGWS). By late 2000, the first
beta versions of .NET 1.0 were released.
In August 2000, Microsoft, Hewlett-Packard, and Intel
worked to standardize CLI and C#. By December 2001,
both were ratified ECMA standards.[1][2]
ISO followed
in April 2003. The current version of ISO standards are
ISO/IEC 23271:2012 and ISO/IEC 23270:2006.[3][4]
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 terms". In addition to meet-
ing these terms, the companies have agreed to make
the patents available royalty-free. However, this did not
apply for the part of .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 imple-
mentations of the full framework.[5]
On 3 October 2007, Microsoft announced that the source
code for .NET Framework 3.5 libraries was to be-
come available under the Microsoft Reference License
(Ms-RSL[lower-alpha 1]
).[6]
The source code repository be-
came available online on 16 January 2008 and included
BCL, ASP.NET, ADO.NET, Windows Forms, WPF and
XML. Scott Guthrie of Microsoft promised LINQ, WCF
and WF libraries were in process of being added.[7]
On 12 November 2014, Microsoft announced .NET
Core, in an effort to include cross-platform support for
.NET, the source release of Microsoft’s CoreCLR imple-
mentation, source for the “entire [...] library stack” for
.NET Core, and the adoption of a conventional (“bazaar"-
like) open source development model under the steward-
ship of the .NET Foundation. Miguel de Icaza describes
.NET Core as a “redesigned version of .NET that is based
on the simplified version of the class libraries”,[8]
and
Microsoft’s Immo Landwerth explained that .NET Core
would be “the foundation of all future .NET platforms”.
At the time of the announcement, the initial release of the
.NET Core project had been seeded with a subset of the
libraries’ source code and coincided with the relicensing
of Microsoft’s existing .NET reference source away from
the restrictions of the Ms-RSL. Landwerth acknowledged
1

2. 2 3 ARCHITECTURE
the disadvantages of the previously selected shared source
license, explaining that it made codename Rotor “a non-
starter” as a community-developed open source project
because it did not meet the criteria of an OSI-approved
license.[9][10][11]
Microsoft also produced an update to its patent grants,
which further extends the scope beyond its previous
pledges. Prior projects like Mono existed in a legal grey
area because Microsoft’s earlier grants applied only to the
technology in “covered specifications”, including strictly
the 4th editions each of ECMA-334 and ECMA-335.
The new patent promise, however, places no ceiling on
the specification version and even extends to any .NET
runtime technologies documented on MSDN that have
not been formally specified by the ECMA group, if a
project chooses to implement them. This permits Mono
and other projects to maintain feature parity with mod-
ern .NET features that have been introduced since the 4th
edition was published without being at risk of patent lit-
igation over the implementation of those features. The
new grant does maintain the restriction that any imple-
mentation must maintain minimum compliance with the
mandatory parts of the CLI specification.[12]
Microsoft’s press release highlights that the cross-
platform commitment now allows for a fully open source,
modern server-side .NET stack. However, Microsoft
does not plan to release the source for WPF or Windows
Forms.[13][14]
2 Versions
Notes:
a.^
.NET Framework 1.0 is integral OS com-
ponent of Windows XP Media Center edition
or Tablet PC edition. Installation CDs for the
Home editions and the Professional editions of
Windows XP SP1, SP2 or SP3 comes with
.NET Framework installation packages.[16]
b.^
Expression Blend only covers the Windows
Presentation Foundation part of .NET Frame-
work 3.0.
c.^ ^ ^
.NET Framework 3.5 is not automat-
ically installed with Windows 8, 8.1 or 10. It
must be installed either from a Windows instal-
lation media or from the Internet on demand.
Control Panel always attempts the latter.[27]
• view
• talk
• edit
Visual overview of the Common Language Infrastructure (CLI)
3 Architecture
3.1 Common Language Infrastructure
Main article: Common Language Infrastructure
Common Language Infrastructure (CLI) provides a
language-neutral platform for application development
and execution, including functions for exception han-
dling, garbage collection, security, and interoperability.
By implementing the core aspects of .NET Framework
within the scope of CLI, this functionality will not be
tied to a single language but will be available across the
many languages supported by the framework. Microsoft’s
implementation of CLI is Common Language Runtime
(CLR). It serves as the execution engine of .NET Frame-
work. All .NET programs execute under the supervision
of CLR, guaranteeing certain properties and behaviors in
the areas of memory management, security, and excep-
tion handling.
For computer programs to run on CLI, they need to be
compiled into Common Intermediate Language (CIL) –
as opposed to being compiled into machine code. Upon
execution, an architecture-specific just-in-time compiler
(JIT) turns the CIL code into machine code. To improve
performance, however, .NET Framework comes with
Native Image Generator (NGEN) that performs ahead-
of-time compilation.

3. 3.5 C++/CLI 3
3.2 Class library
.NET Framework includes a set of standard class li-
braries. The class library is organized in a hierarchy of
namespaces. Most of the built-in APIs are part of ei-
ther System.* or Microsoft.* namespaces. These class
libraries implement a large number of common func-
tions, such as file reading and writing, graphic render-
ing, database interaction, and XML document manipula-
tion, among others. .NET class libraries are available to
all CLI compliant languages. .NET Framework class li-
brary is divided into two parts: Framework Class Library
(FCL) and Base Class Library (BCL).
FCL includes a small subset of the entire class library and
is the core set of classes that serve as the basic API of
CLR.[28]
Classes in mscorlib.dll and some classes in Sys-
tem.dll and System.core.dll are part of FCL. FCL classes
are available in .NET Framework as well as its alternative
implementations including .NET Compact Framework,
Microsoft Silverlight and Mono.
BCL is a superset of FCL and refers to the en-
tire class library that ships with .NET Framework.
It includes an expanded set of libraries, including
Windows Forms, ADO.NET, ASP.NET, Language Inte-
grated Query (LINQ), Windows Presentation Foundation
(WPF), Windows Communication Foundation (WCF)
and Workflow Foundation (WF). BCL is much larger in
scope than standard libraries for languages like C++, and
comparable in scope to standard libraries of Java.
3.3 .NET Core
.NET Core is a free and open-source partial implemen-
tation of the .NET Framework. It consists of CoreCLR
and CoreFX, which are partial forks of CLR and BCL
respectively.[29]
.NET Core comes with an improved just-
in-time compiler, called RyuJIT.[30]
3.4 Assemblies
Compiled CIL code is stored in CLI assemblies. As
mandated by the specification, assemblies are stored in
Portable Executable (PE) file format, common on Win-
dows platform for all DLL and EXE files. Each assembly
consists of one or more files, one of which must contain
a manifest bearing the metadata for the assembly. The
complete name of an assembly (not to be confused with
the file name on disk) contains its simple text name, ver-
sion number, culture, and public key token. Assemblies
are considered equivalent if they share the same complete
name, excluding the revision of the version number.
A private key can also be used by the creator of the as-
sembly for strong naming. The public key token identi-
fies which private key an assembly is signed with. Only
the creator of the keypair (typically .NET developer sign-
ing the assembly) can sign assemblies that have the same
strong name as a previous version assembly, since the cre-
ator is in possession of the private key. Strong naming is
required to add assemblies to Global Assembly Cache.
3.5 C++/CLI
Main article: C++/CLI
Microsoft introduced C++/CLI in Visual Studio 2005,
which is a language and means of compiling Visual C++
programs to run within the .NET Framework. Certain
portions of the C++ program still run within an unman-
aged Visual C++ Runtime, while specially modified por-
tions are translated into CIL code and run with the .NET
Framework’s CLR.
Assemblies compiled using the C++/CLI compiler are
known as mixed-mode assemblies, since they contain na-
tive and managed code within the same DLL.[31]
Such as-
semblies are also difficult to reverse engineer, since .NET
decompilers such as .NET Reflector only reveal the man-
aged code.
4 Design principles
4.1 Interoperability
Because computer systems commonly require interac-
tion between newer and older applications, .NET Frame-
work provides means to access functionality imple-
mented in newer and older programs that execute out-
side .NET environment. Access to COM components
is provided in System.Runtime.InteropServices and Sys-
tem.EnterpriseServices namespaces of the framework ac-
cess to other functionality is achieved using the P/Invoke
feature.
4.2 Language independence
.NET Framework introduces a Common Type Sys-
tem (CTS) that defines all possible datatypes and
programming constructs supported by CLR and how they
may or may not interact with each other conforming to
CLI specification. Because of this feature, .NET Frame-
work supports the exchange of types and object instances
between libraries and applications written using any con-
forming .NET language.
4.3 Portability
While Microsoft has never implemented the full frame-
work on any system except Microsoft Windows, it has en-
gineered the framework to be platform-agnostic,[32]
and

4. 4 4 DESIGN PRINCIPLES
cross-platform implementations are available for other
operating systems (see Silverlight and § Alternative im-
plementations). Microsoft submitted the specifications
for CLI (which includes the core class libraries, CTS, and
CIL),[33][34][35]
C#,[36]
and C++/CLI[37]
to both ECMA
and ISO, making them available as official standards.
This makes it possible for third parties to create compat-
ible implementations of the framework and its languages
on other platforms.
4.4 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 evi-
dence is the source of the assembly (whether it is installed
on the local machine or has been downloaded from the in-
tranet or Internet). CAS uses evidence to determine the
permissions granted to the code. Other code can demand
that calling code be granted a specified permission. The
demand causes CLR to perform a call stack walk: every
assembly of each method in the call stack is checked for
the required permission; if any assembly is not granted
the permission a security exception is thrown.
Managed CIL bytecode is easier to reverse-engineer than
native code, unless obfuscated.[38][39]
NET decompiler
programs enable developers with no reverse-engineering
skills to view the source code behind unobfuscated .NET
assemblies. In contrast, apps compiled to native machine
code are much harder to reverse-engineer and source
code is almost never produced successfully, mainly be-
cause of compiler optimizations and lack of reflection.
One concern is over possible loss of trade secrets and the
bypassing of license control mechanisms. To mitigate
this, Microsoft has included Dotfuscator Community
Edition with Visual Studio .NET since 2002.[lower-alpha 2]
Third-party obfuscation tools are also available from ven-
dors such as vmware, V.i. Labs, Xenocode, Red Gate
Software. Method-level encryption tools for .NET code
are available from vendors such as SafeNet.
4.5 Memory management
CLR frees the developer from the burden of managing
memory (allocating and freeing up when done); it handles
memory management itself by detecting when memory
can be safely freed. Instantiations of .NET types (objects)
are allocated from the managed heap; a pool of memory
managed by CLR. As long as there exists a reference to
an object, which might be either a direct reference to an
object or via a graph of objects, the object is considered
to be in use. When there is no reference to an object, and
it cannot be reached or used, it becomes garbage, eligible
for collection.
.NET Framework includes a garbage collector (GC)
which runs periodically, on a separate thread from the
application’s thread, that enumerates all the unusable ob-
jects and reclaims the memory allocated to them. It is a
non-deterministic, compacting, mark-and-sweep garbage
collector. GC runs only when a certain amount of mem-
ory has been used or there is enough pressure for mem-
ory on the system. Since it is not guaranteed when the
conditions to reclaim memory are reached, GC runs are
non-deterministic. Each .NET application has a set of
roots, which are pointers to objects on the managed heap
(managed objects). These include references to static ob-
jects and objects defined as local variables or method pa-
rameters currently in scope, as well as objects referred
to by CPU registers.[40]
When GC runs, it pauses the ap-
plication, and for each object referred to in the root, it
recursively enumerates all the objects reachable from the
root objects and marks them as reachable. It uses CLI
metadata and reflection to discover the objects encapsu-
lated by an object, and then recursively walk them. It
then enumerates all the objects on the heap (which were
initially allocated contiguously) using reflection. All ob-
jects not marked as reachable are garbage.[40]
This is the
mark phase.[41]
Since the memory held by garbage is not
of any consequence, it is considered free space. However,
this leaves chunks of free space between objects which
were initially contiguous. The objects are then compacted
together to make used memory contiguous again.[40][41]
Any reference to an object invalidated by moving the
object is updated by GC to reflect the new location.[41]
The application is resumed after the garbage collection is
over.
GC used by .NET Framework is also generational.[42]
Objects are assigned a generation; newly created ob-
jects belong to Generation 0. The objects that survive
a garbage collection are tagged as Generation 1, and
the Generation 1 objects that survive another collection
are Generation 2 objects. .NET Framework uses up to
Generation 2 objects.[42]
Higher generation objects are
garbage collected less frequently than lower generation
objects. This helps increase the efficiency of garbage col-
lection, as older objects tend to have a longer lifetime than
newer objects.[42]
Thus, by eliminating older (and thus
more likely to survive a collection) objects from the scope
of a collection run, fewer objects need to be checked and
compacted.[42]
4.6 Simplified deployment
.NET Framework includes design features and tools
which help manage the installation of computer software
to ensure that it does not interfere with previously in-
stalled software, and that it conforms to security require-
ments.

5. 5
4.7 Performance
When an application is first launched, the .NET Frame-
work compiles the CIL code into executable code using
its just-in-time compiler, and caches the executable pro-
gram into the .NET Native Image Cache.[43][44]
Due to
caching, the application launches faster for subsequent
launches, although the first launch is usually slower. To
increase speed of the first launch, developers may use the
Native Image Generator utility to manually compile and
cache any .NET application, ahead-of-time.[44]
The garbage collector, which is integrated into the en-
vironment, can introduce unanticipated delays of execu-
tion over which the developer has little direct control. “In
large applications, the number of objects that the garbage
collector needs to deal with can become very large, which
means it can take a very long time to visit and rearrange
all of them.”[45]
.NET Framework provides support for calling Streaming
SIMD Extensions (SSE) via managed code from April
2014 in Visual Studio 2013 Update 2. However, Mono
has provided support for SIMD Extensions as of ver-
sion 2.2 within the Mono.Simd namespace; before.
Mono’s lead developer Miguel de Icaza has expressed
hope that this SIMD support will be adopted by CLR’s
ECMA standard.[46]
Streaming SIMD Extensions have
been available in x86 CPUs since the introduction of the
Pentium III. Some other architectures such as ARM and
MIPS also have SIMD extensions. In case the CPU lacks
support for those extensions, the instructions are simu-
lated in software.
5 Licensing
Components of .NET Framework are licensed as follows:
6 Alternative implementations
.NET Framework is the predominant implementation of
.NET technologies. Other implementations for parts of
the framework exist. Although the runtime engine is de-
scribed by an ECMA/ISO specification, other implemen-
tations of it may be encumbered by patent issues; ISO
standards may include the disclaimer, “Attention is drawn
to the possibility that some of the elements of this docu-
ment may be the subject of patent rights. ISO shall not
be held responsible for identifying any or all such patent
rights.”[59]
It is more difficult to develop alternatives to
FCL, which is not described by an open standard and may
be subject to copyright restrictions. Additionally, parts
of FCL have Windows-specific functionality and behav-
ior, so implementation on non-Windows platforms can be
problematic.
Some alternative implementations of parts of the frame-
work are listed here.
• .NET Micro Framework is a .NET platform for ex-
tremely resource-constrained devices. It includes
a small version of CLR and supports development
in C# (though some developers were able to use
VB.NET,[60]
albeit with an amount of hacking, and
with limited functionalities) and debugging (in an
emulator or on hardware), both using Microsoft Vi-
sual Studio. It also features a subset of .NET Frame-
work Class Library (about 70 classes with about 420
methods), a GUI framework loosely based on WPF,
and additional libraries specific to embedded appli-
cations.
• Mono is an implementation of CLI and FCL,
and provides additional functionality. It is dual-
licensed under free software and proprietary soft-
ware licenses. It includes support for ASP.NET,
ADO.NET, and Windows Forms libraries for a wide
range of architectures and operating systems. It also
includes C# and VB.NET compilers.
• Portable.NET (part of DotGNU) provides an imple-
mentation of CLI, portions of FCL, and a C# com-
piler. It supports a variety of CPUs and operating
systems.
• Microsoft Shared Source Common Language In-
frastructure is a non-free implementation of CLR.
However, the last version only runs on Microsoft
Windows XP SP2, and was not updated since 2006,
therefore it does not contain all features of version
2.0 of .NET Framework.
• CrossNet[61]
is an implementation of CLI and por-
tions of FCL. It is free software using the open
source MIT License.
7 Notes
[1] The license has previously been abbreviated Ms-RL, but
Ms-RL now refers to the Microsoft Reciprocal License.
[2] Dotfuscator Community Edition 4.0
8 References
[1] “Standard ECMA-335: Common Language Infrastruc-
ture (CLI)". ecma-international.org (6 ed.). ECMA. June
2012.
[2] “Standard ECMA-334: C# Language Specification”.
ecma-international.org (4 ed.). ECMA. June 2006.
[3] “ISO/IEC 23271:2012 Information technology - Com-
mon Language Infrastructure (CLI)". iso.org (3 ed.).
International Organization for Standardization. 13 Febru-
ary 2012.

6. 6 8 REFERENCES
[4] “ISO/IEC 23270:2006 - Information technology - Pro-
gramming languages - C#". iso.org (2 ed.). International
Organization for Standardization. 26 January 2012.
[5] “Microsoft’s Empty Promise”. Free Software Foundation.
16 July 2009. Archived from the original on 5 August
2009. Retrieved 3 August 2009. However, there are sev-
eral 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 Win-
dows Forms. Instead, we're talking about libraries under
the System namespace that provide common functionality
programmers expect in modern programming languages
[6] Guthrie, Scott (3 October 2007). “Releasing the Source
Code for the NET Framework”. Scott Guthrie’s Blog.
Microsoft. Archived from the original on 7 September
2010. Retrieved 15 September 2010.
[7] Guthrie, Scott (16 January 2008). ".NET Framework Li-
brary Source Code now available”. Scott Guthrie’s Blog.
Microsoft. Retrieved 28 February 2015.
[8] de Icaza, Miguel. “Microsoft Open Sources .NET and
Mono”. Personal blog of Miguel de Icaza. Retrieved 16
November 2014.
[9] Landwerth, Immo (12 November 2014). ".NET Core is
Open Source”. .NET Framework Blog. Microsoft. Re-
trieved 30 December 2014.
[10] “dotnet/corefx”. GitHub. Retrieved 16 November 2014.
[11] “Microsoft/referencesource”. GitHub. Retrieved 16
November 2014.
[12] “Microsoft Patent Promise for .NET Libraries and Run-
time Components”. Retrieved 16 November 2014.
[13] “Microsoft takes .NET open source and cross-platform,
adds new development capabilities with Visual Studio
2015, .NET 2015 and Visual Studio Online”. News Cen-
ter. Microsoft. Retrieved 16 November 2014.
[14] Foley, Mary Jo. “Microsoft to open source more of .NET,
and bring it to Linux, Mac OS X”. ZDNet. Retrieved 16
November 2014.
[15] ".NET Framework Versions and Dependencies”. MSDN.
Microsoft. Retrieved 17 January 2014.
[16] Stebner, Aaron (14 March 2007). “Mailbag: What ver-
sion of the .NET Framework is included in what version
of the OS?". Aaron Stebner’s WebLog. Microsoft.
[17] “What’s New in Visual Studio .NET 2003”. MSDN.
Microsoft. Retrieved 1 September 2014. Visual Studio
.NET 2002 shipped with the Microsoft .NET Framework
SDK version 1.0. Visual Studio .NET 2003 ships with
.NET Framework SDK version 1.1.
[18] ".NET Framework Developer Center – Frequently Asked
Questions”. Archived from the original on July 24, 2012.
[19] “What’s New in Visual Studio 2005”. MSDN. Microsoft.
Retrieved 1 September 2014.
[20] “What’s New in Windows Server 2003 R2”. TechNet.
Microsoft. 22 August 2005. Retrieved 5 January 2015.
[21] Chinnathambi, Kirupa (4 December 2006). “Expression
Blend -- What Is That?". Expression Blend and Design.
Microsoft. Retrieved 1 September 2014.
[22] Guthrie, Scott (19 November 2007). “Visual Studio 2008
and .NET 3.5 Released”. Scott Gu’s Blog. Microsoft. Re-
trieved 1 September 2014.
[23] “What’s New in Visual Studio 2010”. MSDN. Microsoft.
Retrieved 1 September 2014.
[24] “What’s New in Visual Studio 2012”. MSDN. Microsoft.
Retrieved 1 September 2014.
[25] “What’s New in Visual Studio 2013”. MSDN. Microsoft.
Retrieved 1 September 2014.
[26] Somasegar, S (29 June 2015). “Save the Date: Vi-
sual Studio 2015 RTM on July 20th”. Somasegar’s blog.
Microsoft.
[27] “Installing the .NET Framework 3.5 on Windows 8, Win-
dows 8.1 and Windows 10”. MSDN. Microsoft. Archived
from the original on 27 April 2015.
[28] “Base Class Library”. Retrieved 1 June 2008.
[29] Landwerth, Immo (4 December 2014). “Introducing
.NET Core”. .NET Framework Blog. Microsoft. Re-
trieved 27 February 2015.
[30] Landwerth, Immo (3 February 2015). “CoreCLR is now
Open Source”. .NET Framework Blog. Microsoft. Re-
trieved 27 February 2015.
[31] Mixed (Native and Managed) Assemblies, MSDN
[32] “Scott Guthrie: Silverlight and the Cross-Platform CLR”.
Channel 9. 30 April 2007. Archived from the original on
2015-03-25. Retrieved 2015-02-20.
[33] “ECMA 335 - Standard ECMA-335 Common Language
Infrastructure (CLI)". ECMA. 1 June 2006. Archived
from the original on 14 June 2008. Retrieved 1 June 2008.
[34] “ISO/IEC 23271:2006”. Standards.iso.org. 29 Septem-
ber 2006. Retrieved 17 April 2012.
[35] “Technical Report TR/84 Common Language Infrastruc-
ture (CLI) - Information Derived from Partition IV XML
File”. ECMA. 1 June 2006. Archived from the original
on 2015-03-25. Retrieved 2015-02-20.
[36] “ECMA-334 C# Language Specification”. ECMA. 1 June
2006.
[37] “Standard ECMA-372 C++/CLI Language Specifica-
tion”. ECMA. 1 December 2005.
[38] “Reverse Engineering Risk Assessment” (PDF).
[39] Gartner, Inc. as reported in “Hype Cycle for Cy-
berthreats, 2006”, September 2006, Neil MacDonald;
Amrit Williams, et al.

7. 7
[40] “Garbage Collection: Automatic Memory Management
in the Microsoft .NET Framework”. Archived from the
original on 3 July 2007. Retrieved 1 June 2008.
[41] “Garbage collection in .NET”. Archived from the original
on 25 May 2008. Retrieved 1 June 2008.
[42] “Garbage Collection—Part 2: Automatic Memory Man-
agement in the Microsoft .NET Framework”. Archived
from the original on 26 June 2007. Retrieved 1 June 2008.
[43] Understanding .NET Just-In-Time Compilation, Telerik
[44] Compiling MSIL to Native Code, MSDN, Microsoft
[45] “Understanding Garbage Collection in .NET”.
[46] "Mono’s SIMD Support: Making Mono safe for Gaming".
Tirania.org. 3 November 2008. Retrieved 17 April 2012.
[47] ".NET Core 5”. dotnetfoundation.org. .NET Foundation.
Retrieved 17 February 2015.
[48] ".NET Micro Framework”. dotnetfoundation.org. .NET
Foundation. Retrieved 17 February 2015.
[49] ".NET Compiler Platform (“Roslyn”)". dotnetfounda-
tion.org. .NET Foundation. Retrieved 17 February 2015.
[50] “ASP.NET 5”. dotnetfoundation.org. .NET Foundation.
Retrieved 17 February 2015.
[51] “ASP.NET MVC, Web API and Web Pages (Razor)".
dotnetfoundation.org. .NET Foundation. Retrieved 17
February 2015.
[52] “ASP.NET Ajax Control Toolkit”. dotnetfoundation.org.
.NET Foundation. Retrieved 17 February 2015.
[53] “ASP.NET SignalR”. dotnetfoundation.org. .NET Foun-
dation. Retrieved 17 February 2015.
[54] “Entity Framework 6”. dotnetfoundation.org. .NET
Foundation. Retrieved 17 February 2015.
[55] “NuGet”. dotnetfoundation.org. .NET Foundation. Re-
trieved 17 February 2015.
[56] Bray, Brandon (15 August 2012). “Announcing the re-
lease of .NET Framework 4.5 RTM - Product and Source
Code”. .NET Framework Blog. Microsoft.
[57] “Announcing .NET 2015 Preview: A New Era for .NET”.
.NET Framework Blog. Microsoft. 12 November 2014.
[58] “Microsoft .NET Framework Redistributable EULA”.
MSDN. Microsoft. Retrieved 28 February 2015.
[59] ISO 9001:2008, Foreword
[60] “Using VB.NET with the .NET Micro Framework «
/dev/mobile”. Christec.co.nz. 1 April 2008. Retrieved
17 April 2012.
[61] “CrossNet”. Codeplex.com. Retrieved 17 April 2012.
9 External links
• Official website
• .NET Framework Developer Center on
MSDN Library
• .NET Framework Index
• Overview of .NET Framework (MSDN)
• .NET Framework FAQ
• .NET Github repository

8. 8 10 TEXT AND IMAGE SOURCES, CONTRIBUTORS, AND LICENSES
10 Text and image sources, contributors, and licenses
10.1 Text
• .NET Framework Source: https://en.wikipedia.org/wiki/.NET_Framework?oldid=680743964 Contributors: Damian Yerrick, Joakim
Ziegler, Mav, The Anome, Ffaker, Youssefsan, Walter, Enchanter, William Avery, ChangChienFu, Maury Markowitz, Ellmist, Heron,
Rlee0001, Hirzel, Hephaestos, Jim McKeeth, Nevilley, Frecklefoot, JohnOwens, Modster, DopefishJustin, Nixdorf, Mdupont, Wwwwolf,
BjarkeDahlEbert, Gbleem, SebastianHelm, Minesweeper, Alfio, Dmb~enwiki, Ahoerstemeier, KAMiKAZOW, Mac, Lovely Chris, Ronz,
LittleDan, Julesd, Susurrus, Kaihsu, Cryoboy, Marknew, Edaelon, Ed Brey, Dwo, Feedmecereal, Timwi, RickK, Viajero, Magnus.de,
Dysprosia, Jay, Timc, Quux, Markhurd, Furrykef, Fibonacci, Bevo, Shizhao, Stormie, Northgrove, Robbot, MrJones, Noldoaran, Moriori,
RedWolf, Altenmann, Samrolken, Academic Challenger, Yacht, Cyril~enwiki, Hadal, Wereon, Pps, Diberri, Mattflaschen, Dina, Tobias
Bergemann, Mlk, ManuelGR, Unfree, Ancheta Wis, Somercet, Giftlite, Marius~enwiki, Laudaka, Sepreece, Mintleaf~enwiki, Haeleth, Art
Carlson, Fleminra, Dratman, Malekith~enwiki, Gracefool, Rchandra, AlistairMcMillan, Darin, Matt Crypto, Fayssal FERTAKH, Uzume,
Mckaysalisbury, Bobblewik, Christopherlin, Thijs!, Wmahan, Neilc, Masterhomer, Gadfium, Alexf, PDH, Mark5677, OwenBlacker, Kevin
B12, Cynical, Adrian Sampson, Kutulu, MementoVivere, Onebit, EagleOne, Corti, Njh@bandsman.co.uk, Mormegil, Discospinster, El-
Tyrant, Rich Farmbrough, Nma wiki, Deh, Smyth, Cagliost, Notinasnaid, Mjpieters, Wizzardmr42, Harriv, Kenb215, Elykyllek, Compie,
Plugwash, Flib0, CanisRufus, Zenohockey, Surachit, Sietse Snel, Triona, Perfecto, PatrikR, Bobo192, NetBot, Longhair, Sdaconsulting,
Flxmghvgvk, RAM, Blakkandekka, Flashmob, Apoltix, Cwolfsheep, Adrian~enwiki, Gingko, Greenleaf~enwiki, SpeedyGonsales, Nk,
Raja99, Minghong, Zidler~enwiki, NeilSantos, JesseHogan, Nsaa, Mroach, Storm Rider, Richardsonke, Alansohn, Gary, Uncle.bungle,
Jic, Arthena, CyberSkull, Atlant, Jeltz, Jtalledo, Mmmready, Wjw, Calton, MikeWeiner, Kocio, B3virq3b, Judik, Kraenar, Snowolf,
GeorgeStepanek, KJK::Hyperion, Velella, Ronark, Suruena, Garzo, RainbowOfLight, Bsadowski1, Computerjoe, Ceyockey, Tiger Khan,
Forderud, Bruce89, Mahanga, Dtobias, Alkarex, Cheungpat, Camw, Nuggetboy, Uncle G, Michael R Bax, Terence, Nikiforov, Tomabuct,
Bluemoose, Santiago Roza (Kq), Crpietschmann, Kriegman, Sega381, J M Rice, Toussaint, Behun, Kesla, Graham87, Yurik, DePiep,
Jclemens, Mendaliv, Enzo Aquarius, Ryan Norton, Ketiltrout, Kephart, Sjö, Rjwilmsi, Joe Decker, Altacus, XP1, Amire80, RMo, Eric
Burnett, SMC, Ligulem, Fred Bradstadt, SNIyer12, Saksham, FayssalF, Titoxd, FlaBot, Skyfiler, SchuminWeb, Intersofia, Ysangkok, Brian-
reading, Mathiastck, Chanting Fox, RexNL, Ewlyahoocom, AdunaicLayman, Riki, Snailwalker, Imnotminkus, Frjwoolley, Typhoonhurri-
cane, Chobot, RJSampson, DVdm, Random user 39849958, Bgwhite, Peterl, Gwernol, Elfguy, YurikBot, Borgx, Daverocks, JustSomeKid,
Phantomsteve, RussBot, Hyad, IByte, Rodasmith, Matt Fitzpatrick, Noypi380, Stephenb, Almogo, The1physicist, CambridgeBayWeather,
Rsrikanth05, Akhristov, Member, LauriO~enwiki, Richard Allen, TEB728, WulfTheSaxon, Miguel.de.Icaza, AKeen, ZacBowling, Fu-
turix, Anetode, Bert Macklin, Brandon, Peter Delmonte, CecilWard, InvaderJim42, Cnu2k5, Voidxor, Marc44, SixSix, Leotohill, Foofy,
Gadget850, Rwalker, Erpe, CorbieVreccan, Jeremy Visser, Pelister, Xpclient, Werdna, Googl, Destructionator, BMT, Paul Magnussen,
KartoumHero, Zzuuzz, RamirBorja, Brian Tvedt, Tvarnoe~enwiki, Sean Whitton, CWenger, Rickz0rz, Tenox, JLaTondre, Memodude,
ViperSnake151, Allens, Chip Zero, Mebden, Dondemuth, Tyomitch, GrinBot~enwiki, Dan Atkinson, Superrcat, Liujiang, Tom Morris,
Sycthos, EJSawyer, SmackBot, Lashiec, Ratarsed, Kellen, Chris Burrows, Reedy, InverseHypercube, Hydrogen Iodide, Basil.bourque,
Jacek Kendysz, KocjoBot~enwiki, BurntSky, Eskimbot, Sydius, CapitalSasha, Dbnull, McoreD, Xaosflux, Gilliam, Donama, Ppntori,
Konstantin Veretennicov, Jcarroll, ERcheck, Evilandi, JAn Dudík, Marc Kupper, PetrochemicalPete, Bluebot, Optikos, DStoykov, Morte,
Adamralph, Akanemoto, Jimmyzimms, ChristopherM, Gracenotes, MaxSem, Audriusa, Saiswa, Can't sleep, clown will eat me, Robogun,
Frap, Cyberjessy, KevM, Wikipedia brown, KerathFreeman, Ddon, BWCNY, Ortzinator, Cybercobra, Rsatter, Dvanderboom, Localzuk,
Warren, Leaflord, DMacks, Rexmorgan, Mitchumch, Jonnyapple, Kcargile, Tfl, Tobiasly, Jonmmorgan, G-Bot~enwiki, Craig Bolon, Ar-
glebargleIV, Doug Bell, Harryboyles, Gnj, Kuru, Bizzako, Microchip08, MagnaMopus, Soumyasch, Watson Ladd, Sundström, Minna
Sora no Shita, Codepro, Diverman, Jake-helliwell, Caviare, Ian Dalziel, Zout, Slakr, Stwalkerster, UKER, Xiaphias, Optakeover, In-
quisitus, Carlo.milanesi, Wikimsd, RtpHarry, Hu12, White Ash, Iridescent, Remon sherin, J Di, Snoutholder, UncleDouggie, Vanished
user h4iwrg8h2w34triuoaefkjnsv3, Linkspamremover, Illyria05, Eluchil404, Jack’s Revenge, FatalError, SkyWalker, Xcentaur, FleetCom-
mand, CmdrObot, Nysin, Dycedarg, Scohoust, Mitchello, WeggeBot, Abhishek2617, JamesNK, Alexignatiou~enwiki, Lyml, Cydebot,
Djg2006, ST47, Solidpoint, Mgiann, CritterNYC, ClinkingDog, Tawkerbot4, Shirulashem, Christian75, Torc2, Xtv, Kozuch, Ike-bana,
Legotech, Thijs!bot, Epbr123, Brijen911, Gaijin42, Qwyrxian, Chitomcgee, Hervegirod, Vanished user 07, RussPitcher, Marek69, On-
drejsv, Wiki fanatic, Jayrvox, JustAGal, Jsnover, Zachary, GehennaNL, JJ.Lin, Petrtom, Ziggurism, Natalie Erin, Mmortal03, Porqin, Ed-
Jogg, AntiVandalBot, Widefox, Nshuks7, Seaphoto, Sean.woodward, Shinsuk, Harborsparrow, AlexOvShaolin, LibLord, Kprobst, Myanw,
Small island, JAnDbot, MER-C, Sitethief, SimonFlummox, Hut 8.5, Rgsiii, Kerotan, Flameass, Magioladitis, VoABot II, Askari Mark,
Rhwawn, AtticusX, JamesBWatson, Jimbluedog, TiagoDias, Janadore, MKFM, Arjunsridharur, Jjegers, 28421u2232nfenfcenc, Allstare-
cho, Jehjoa, XMog, Shalvin P D, Mfloryan, Granburguesa, Aldenrw, Donsez, DerHexer, Kovyrin, Bahder, Demono, Eamon914, Gwern,
Stephenchou0722, Fduch, Ravichandar84, HorseShoe, Hasruf, Corgi5623, Stimpy77, J.delanoy, Willardjuice, CSharp-Online.NET Editor,
Ijustam, Heath007, Christopher G Lewis, Bcartolo, Dispenser, Andrewtechhelp, Philmatic, Buxley Hall, McSly, Nevalex, Jutiphan, Plas-
ticup, Mfb52, Engfelt, NewEnglandYankee, Alnokta, Erik Swanson, Smitty, Entropy, Jamesontai, Remember the dot, DenisBach~enwiki,
Escla, Tagus, Nimrand, Kvdveer, MartinRinehart, Varnent, Onkelringelhuth, Teacurran, Steel1943, Asherkobin, Vikasgoyal77, Aaa839,
Numberp, Mrh30, Dan.tsafrir, Philip Trueman, Drjonesgp, Kr-val, TXiKiBoT, Red Act, Calwiki, Technopat, PonThePony, Tuanese,
Arnon Chaffin, Qxz, Coldfire82, Cody-7, Michael Hodgson, Anna Lincoln, Lradrama, Imasleepviking, Eviktor, Jackfork, Noforma-
tion, Findling67, JunkDNA, Thanosd, Ilyaroz, Staka, Kai, Annaellis, Michelleem, Triggersite, Logan, Gbjbaanb, ObitheWan, S.Örvarr.S,
GoddersUK, SieBot, Leirith, Borgdylan, Jesdisciple, Op12, Josh the Nerd, Caltas, Triwbe, Jerryobject, Bentogoa, Flyer22, Elcobbola,
Zurqoxn, Oxymoron83, Lightmouse, Hobartimus, Venkat 9009, Tbrill5, Alex.muller, Kumioko (renamed), Svick, Masonwheeler, Sil-
vergoat, ConfusedSushi, ZikiCZ, Bijoysr, Leotohell, Nn123645, Markcrosbie, XDanielx, Martarius, Sfan00 IMG, Zhengjp, ClueBot,
Helpsloose, CiudadanoGlobal, Jerry Wright, The Thing That Should Not Be, Helenabella, Ndenison, TheRasIsBack, Mailtojp, Adrianwn,
Razimantv, Wikimike2007, OlivierNallet, Vinitfichadia, Shinji14~enwiki, Frank Hileman, Dlunch, EscapeTechwriter, Campoftheamer-
icas, Mnikoo, DavidBlackwell, Excirial, Naerii, Anon lynx, CRobClark, Robertbrichter, Abrech, Wilsone9, Techeeee, Mike.rooke, Sun
Creator, Vamsankar, Chininazu12, Noosentaal, CodeCaster, Jamestochter, Richard.szalay, Mbjencyclopedia, Lawrenceteo, DanielPharos,
Unused000706, GFHandel, Anthall1991, Jacques Bergeron~enwiki, Versus22, Porchcorpter, Johnuniq, SoxBot III, Skunkboy74, Dylan-
fromthenorth, XLinkBot, Nblumhardt, Kasutt, Gonzonoir, Tbsdy lives, C. A. Russell, Mitch Ames, Skarebo, WikHead, Mifter, Cakruege,
PL290, Karpouzi, Alexius08, Idolescent, Gggh, Johndci, Addbot, Proofreader77, Ramu50, Mortense, ConCompS, Yoenit, Tcncv, Rob-
bieAB, FeRD NYC, Aecy, Rapidshare, JRtheDude, Cst17, MrOllie, CarsracBot, Glane23, Theking9794, Kinamand, TheFattest, Zeal-
ousCoder, Evildeathmath, Tide rolls, Jarble, Nicolas Love, PhilipMay, Luckas-bot, Yobot, Themfromspace, Kartano, Fraggle81, Cflm001,
Legobot II, Eazulay, Riad.Bot~enwiki, MrBlueSky, Wonderfl, The locster, AnomieBOT, Rubinbot, 1exec1, Fox Aquatis, Killiondude, IRP,
Billegge, JackieBot, Piano non troppo, Keithbob, Flewis, Materialscientist, Puhfyn, Muthu1809, Felyza, ArthurBot, Xqbot, Rao mocharla,
Lprd2007, Capricorn42, Drilnoth, Millahnna, Jgyanendra, Ideaclimber, Prunesqualer, RibotBOT, Janagewen, Cresvi, A Quest For Knowl-

9. 10.2 Images 9
edge, Bo98, Shadowjams, WebCiteBOT, Iggymwangi, Manish014, PCrew00, FrescoBot, Wei.cs, Minooch, StaticVision, Mhadi.afrasiabi,
Baskus, Ctrautman1, Wandering-teacher, Amplitude101, Winterst, SpacemanSpiff, I dream of horses, 10metreh, Jaysmith2108, Ha-
laelkholy, Justpossible, Calmer Waters, Hamtechperson, Ngyikp, Rafaelluik, Ioakar, Ongar the World-Weary, SpaceFlight89, Tcnuk, Beao,
GoneIn60, Bgpaulus, Maw136, Riccardo.fabris, Anil235, Tim1357, Martyn Lovell, Lotje, Vrenator, Moonwolf14, Reaper Eternal, Jef-
frd10, Galestar, Some Wiki Editor, Reach Out to the Truth, DARTH SIDIOUS 2, Mean as custard, Bento00, Manpal78, Ripchip Bot,
Halestock, Fitoschido, Drysart, Nistra, DASHBot, Himanet, John of Reading, Abdulsami20, Immunize, Booler80, Noloader, Petermarcu,
GoingBatty, RA0808, Mrcarter8, RenamedUser01302013, DiiCinta, Tommy2010, K6ka, AsceticRose, Robert.maclean, Akshaykumard-
wivedi, Billy9999, SVG, Vicky4ud, DonToto, H3llBot, Khishig.s, Mcmatter, Tolly4bolly, Tomy9510, Mayur, Ipapasa, Eldenf, Digvijay-
pundir1, ChuispastonBot, Volvov70, 28bot, Rocketrod1960, Ebehn, Petrb, Kypr8, ClueBot NG, Gareth Griffith-Jones, Jack Greenmaven,
Matthiaspaul, MelbourneStar, Pizza1016, Gilderien, Satellizer, Kikichugirl, Shaddim, Kragen2uk, MahendraSonwane, Tkumarabhishek,
Widr, Exadrid, Gauravsingh2890, Helpful Pixie Bot, පසිඳු කාවින්ද, BG19bot, Northamerica1000, Kumsarav, Wiki13, MusikAnimal, Joy-
deep, Visuall, Chmarkine, KermitBeaufort, Shubh9795, Sandbergja, Wannabemodel, Strz4life, BattyBot, Nitinmarwal, W.D., Ushau97,
‫,اقرأ‬ Dexbot, Rezonansowy, Codename Lisa, Karl Magnus, Kooginup, Sigvit, Lugia2453, Frosty, SolidSnake110, Corn cheese, The Anony-
mouse, Faizan, Spyglasses, Ginsuloft, Quenhitran, Pysimpler, OccultZone, BounceBack Data Recovery, Lakun.patra, Skr15081997, Veir-
timid, DaFLM, Omewiki, Amortias, Wagnerp16, Matkec, CookieMonster755, Manikandan5691, Tejinder90, Nickyp1990, Tijmen Wil,
Testuserplzignore, Dettifoss, Rachika Mishra, Paavohtl, Cskarthik, Theayushsharma, JeremiahY and Anonymous: 1837
10.2 Images
• File:DotNet.svg Source: https://upload.wikimedia.org/wikipedia/commons/d/d3/DotNet.svg License: CC-BY-SA-3.0 Contributors: Own
work Original artist: Soumyasch
• File:Folder_Hexagonal_Icon.svg Source: https://upload.wikimedia.org/wikipedia/en/4/48/Folder_Hexagonal_Icon.svg License: Cc-by-
sa-3.0 Contributors: ? Original artist: ?
• File:Microsoft_.NET_Framework_v4.5_logo.png Source: https://upload.wikimedia.org/wikipedia/en/0/0d/Microsoft_.NET_
Framework_v4.5_logo.png License: Fair use Contributors:
http://blogs.msdn.com/blogfiles/jimoneil/WindowsLiveWriter/StayingInformed_AFB5/NET_h_rgb_2.png Original artist: ?
• File:Overview_of_the_Common_Language_Infrastructure.svg Source: https://upload.wikimedia.org/wikipedia/commons/8/85/
Overview_of_the_Common_Language_Infrastructure.svg License: Public domain Contributors: Own work Original artist: Jarkko
Piiroinen
• File:Symbol_list_class.svg Source: https://upload.wikimedia.org/wikipedia/en/d/db/Symbol_list_class.svg License: Public domain Con-
tributors: ? Original artist: ?
• File:Wikibooks-logo-en-noslogan.svg Source: https://upload.wikimedia.org/wikipedia/commons/d/df/Wikibooks-logo-en-noslogan.
svg License: CC BY-SA 3.0 Contributors: Own work Original artist: User:Bastique, User:Ramac et al.
• File:Wikiversity-logo.svg Source: https://upload.wikimedia.org/wikipedia/commons/9/91/Wikiversity-logo.svg License: CC BY-SA 3.0
Contributors: Snorky (optimized and cleaned up by verdy_p) Original artist: Snorky (optimized and cleaned up by verdy_p)
10.3 Content license
• Creative Commons Attribution-Share Alike 3.0