.NET Framework

This article is about the Microsoft technology. For the Top-level domain, see .net. For other uses, see .NET.

.NET Framework

Developer(s)	Microsoft
Initial release	13 February 2002; 9 years ago (2002-02-13)
Stable release	4.0 (4.0.30319.1) / 12 April 2010; 19 months ago (2010-04-12)
Preview release	4.5 / 13 September 2011; 2 months ago (2011-09-13)
Operating system	Windows 98 or later, Windows NT 4.0 or later
Type	Software framework
License	MS-EULA, BCL under Microsoft Reference Source License[1]
Website	msdn.microsoft.com/netframework

The .NET Framework (pronounced dot net) is a software framework that runs primarily on Microsoft Windows. It includes a large library and supports several programming languages which allows language interoperability (each language can use code written in other languages). Programs written for the .NET Framework execute in a software environment (as contrasted to hardware environment), known as the Common Language Runtime (CLR), an application virtual machine that provides important services such as security, memory management, and exception handling. The class library and the CLR together constitute the .NET Framework.

The .NET Framework's Base Class Library provides user interface, data access, database connectivity, cryptography, web application development, numeric algorithms, and network communications. Programmers produce software by combining their own source code with the .NET Framework and other libraries. The .NET Framework is intended to be used by most new applications created for the Windows platform. Microsoft also produces a popular integrated development environment largely for .NET software called Visual Studio.

History

Main article: .NET Framework version history

The .NET Framework stack.

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.^[2]

Version 3.0 of the .NET Framework is included with Windows Server 2008 and Windows Vista. Version 3.5 is included with Windows 7, and can also be installed on Windows XP and the Windows Server 2003 family of operating systems.^[3] On April 12, 2010, .NET Framework 4 was released alongside Visual Studio 2010.

The .NET Framework family also includes two versions for mobile or embedded device use. A reduced version of the framework, the .NET Compact Framework, is available on Windows CE platforms, including Windows Mobile devices such as smartphones. Additionally, the .NET Micro Framework is targeted at severely resource-constrained devices.

Version	Version Number	Release Date	Visual Studio	Default in Windows
1.0	1.0.3705.0	2002-02-13	Visual Studio .NET	Windows XP Tablet and Media Center Editions[4]
1.1	1.1.4322.573	2003-04-24	Visual Studio .NET 2003	Windows Server 2003
2.0	2.0.50727.42	2005-11-07	Visual Studio 2005	Windows Server 2003 R2
3.0	3.0.4506.30	2006-11-06		Windows Vista, Windows Server 2008
3.5	3.5.21022.8	2007-11-19	Visual Studio 2008	Windows 7, Windows Server 2008 R2
4.0	4.0.30319.1	2010-04-12	Visual Studio 2010
4.5	4.5.40805	2011-09-13 (Developer Preview)	Visual Studio '11'	Windows 8, Windows Server 8

A more complete listing of the releases of the .NET Framework may be found on the List of .NET Framework versions.

Design features

Interoperability

Because computer systems commonly require interaction between new and older applications, the .NET Framework provides means to access functionality that is implemented in programs that execute outside the .NET environment. Access to COM components is provided in the System.Runtime.InteropServices and System.EnterpriseServices namespaces of the framework; access to other functionality is provided using the P/Invoke feature.

Common Language Runtime Engine

The Common Language Runtime (CLR) is the execution engine of the .NET Framework. All .NET programs execute under the supervision of the CLR, guaranteeing certain properties and behaviors in the areas of memory management, security, and exception handling.

Language Independence

The .NET Framework introduces a Common Type System, or CTS. The CTS specification defines all possible datatypes and programming constructs supported by the CLR and how they may or may not interact with each other conforming to the Common Language Infrastructure (CLI) specification. Because of this feature, the .NET Framework supports the exchange of types and object instances between libraries and applications written using any conforming .NET language.

Base Class Library

The Base Class Library (BCL), part of the Framework Class Library (FCL), is a library of functionality available to all languages using the .NET Framework. The BCL provides classes which encapsulate a number of common functions, including file reading and writing, graphic rendering, database interaction, XML document manipulation and so on.

Simplified Deployment

The .NET Framework includes design features and tools that help manage the installation of computer software to ensure that it does not interfere with previously installed software, and that it conforms to security requirements.

Security

The design is meant to address some of the vulnerabilities, such as buffer overflows, that have been exploited by malicious software. Additionally, .NET provides a common security model for all applications.

Portability

While Microsoft has never implemented the full framework on any system except Microsoft Windows, the framework is engineered to be platform agnostic,^[5] and cross-platform implementations are available for other operating systems (see Silverlight and the Alternative implementations section below). Microsoft submitted the specifications for the Common Language Infrastructure (which includes the core class libraries, Common Type System, and the Common Intermediate Language),^[6][7][8] the C# language,^[9] and the C++/CLI language^[10] to both ECMA and the ISO, making them available as open standards. This makes it possible for third parties to create compatible implementations of the framework and its languages on other platforms.

Architecture

Visual overview of the Common Lann guage Infrastructure (CLI)

Common Language Infrastructure (CLI-Amer)

Main article: Common Language Infrastructure

The purpose of the Common Language Infrastructure (CLI) is to provide a language-neutral platform for application development and execution, including functions for Exception handling, Garbage Collection, security, and interoperability. By implementing the core aspects of the .NET Framework within the scope of the 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 the CLI is called the Common Language Runtime, or CLR.

Main article: .NET assembly

The lowest-level human-readable programming language defined by the CLI specification is called the Common Intermediate Language (CIL). The CIL code is housed in .NET assemblies. As mandated by specification, assemblies are stored in the Portable Executable (PE) format, common on the Windows platform for all DLL and EXE files. The assembly consists of one or more files, one of which must contain the manifest, which has the metadata for the assembly. The complete name of an assembly (not to be confused with the filename on disk) contains its simple text name, version number, culture, and public key token. The public key token is a unique hash generated when the assembly is compiled, thus two assemblies with the same public key token are guaranteed to be identical from the point of view of the framework.^{[dubious – discuss]} A private key can also be specified known only to the creator of the assembly and can be used for strong naming and to guarantee that the assembly is from the same author when a new version of the assembly is compiled (required to add an assembly to the Global Assembly Cache).

Security

.NET has its own security mechanism with two general features: Code Access Security (CAS), and validation and verification. Code Access Security 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 intranet or Internet). Code Access Security uses evidence to determine the permissions granted to the code. Other code can demand that calling code is granted a specified permission. The demand causes the 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.

Class library

Namespaces in the BCL[11]
System
System. CodeDom
System. Collections
System. Diagnostics
System. Globalization
System. IO
System. Resources
System. Text
System. Text.RegularExpressions

See also: Base Class Library and Framework Class Library

The .NET Framework includes a set of standard class libraries. The class library is organized in a hierarchy of namespaces. Most of the built in APIs are part of either System.* or Microsoft.* namespaces. These class libraries implement a large number of common functions, such as file reading and writing, graphic rendering, database interaction, and XML document manipulation, among others. The .NET class libraries are available to all CLI compliant languages. The .NET Framework class library is divided into two parts: the Base Class Library and the Framework Class Library.

The Base Class Library (BCL) includes a small subset of the entire class library and is the core set of classes that serve as the basic API of the Common Language Runtime.^[11] The classes in mscorlib.dll and some of the classes in System.dll and System.core.dll are considered to be a part of the BCL. The BCL classes are available in both .NET Framework as well as its alternative implementations including .NET Compact Framework, Microsoft Silverlight and Mono.

The Framework Class Library (FCL) is a superset of the BCL classes and refers to the entire class library that ships with .NET Framework. It includes an expanded set of libraries, including Windows Forms, ADO.NET, ASP.NET, Language Integrated Query, Windows Presentation Foundation, Windows Communication Foundation among others. The FCL is much larger in scope than standard libraries for languages like C++, and comparable in scope to the standard libraries of Java.

Memory management

The .NET Framework CLR frees the developer from the burden of managing memory (allocating and freeing up when done); instead it does the memory management itself by detecting when memory can be safely freed. Memory is allocated to instantiations of .NET types (objects) from the managed heap, a pool of memory managed by the 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 which runs periodically, on a separate thread from the application's thread, that enumerates all the unusable objects and reclaims the memory allocated to them.

The .NET Garbage Collector (GC) is a non-deterministic, compacting, mark-and-sweep garbage collector. The GC runs only when a certain amount of memory has been used or there is enough pressure for memory on the system. Since it is not guaranteed when the conditions to reclaim memory are reached, the 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 objects and objects defined as local variables or method parameters currently in scope, as well as objects referred to by CPU registers.^[12] When the GC runs, it pauses the application, 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 .NET metadata and reflection to discover the objects encapsulated 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 objects not marked as reachable are garbage.^[12] This is the mark phase.^[13] 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.^[12][13] Any reference to an object invalidated by moving the object is updated by the GC to reflect the new location.^[13] The application is resumed after the garbage collection is over.

The GC used by .NET Framework is actually generational.^[14] Objects are assigned a generation; newly created objects 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. The .NET Framework uses up to Generation 2 objects.^[14] Higher generation objects are garbage collected less frequently than lower generation objects. This helps increase the efficiency of garbage collection, as older objects tend to have a larger lifetime than newer objects.^[14] Thus, by removing 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.^[14]

Standardization and licensing

In August 2000, Microsoft, Hewlett-Packard, and Intel worked to standardize CLI and the C# programming language. By December 2001, both were ratified ECMA standards (ECMA 335 and ECMA 334). ISO followed in April 2003 - the current version of the ISO standards are ISO/IEC 23271:2006 and ISO/IEC 23270:2006.^[15][16]

While Microsoft and their partners hold patents^{[citation needed]} for the 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 meeting these terms, the companies have agreed to make the patents available royalty-free.^{[citation needed]}

However, this does not apply for the part of the .NET Framework which is not covered by the ECMA/ISO standard, which includes Windows Forms, ADO.NET, and ASP.NET. Patents that Microsoft holds^{[citation needed]} in these areas may deter non-Microsoft implementations of the full framework.^[17]

On 3 October 2007, Microsoft announced that much of the source code for the .NET Framework Base Class Library (including ASP.NET, ADO.NET, and Windows Presentation Foundation) was to have been made available with the final release of Visual Studio 2008 towards the end of 2007 under the shared source Microsoft Reference License.^[1] The source code for other libraries including Windows Communication Foundation (WCF), Windows Workflow Foundation (WF), and Language Integrated Query (LINQ) were to be added in future releases. Being released under the non-open source Microsoft Reference License means this source code is made available for debugging purpose only, primarily to support integrated debugging of the BCL in Visual Studio.

Criticism

Some concerns and criticism relating to .NET include:

• Applications running in a managed environment tend to require more system resources than similar applications that access machine resources more directly.
• Unobfuscated managed CIL bytecode can often be easier to reverse-engineer than native code.^[18][19] One concern is over possible loss of trade secrets and the bypassing of license control mechanisms. Since Visual Studio .NET (2002), Microsoft has included a tool to obfuscate code (Dotfuscator Community Edition).^[20]
• Newer versions of the framework (3.5 and up) are not pre-installed in versions of Windows below Windows 7 (although newer versions are available via Windows Update). For this reason, applications must lead users without the framework through a procedure to install it. Some developers have expressed concerns about the large size of the .NET Framework runtime installers for end-users. The size is around 54 MB for .NET 3.0, 197 MB for .NET 3.5, and 250 MB for .NET 3.5 SP1 (while using web installer the typical download for Windows XP is around 50 MB, for Windows Vista - 20 MB). The size issue is partially solved with .NET 4 installer (x86 + x64) being 54 MB and not embedding full runtime installation packages for previous versions. The .NET 3.5 SP1 full installation package includes the full runtime installation packages for .NET 2.0 SP2 as well as .NET 3.0 SP2 for multiple operating systems (Windows XP/Server 2003 and Windows Vista/Server 2008) and for multiple CPU architectures (x86, x86-64, and IA-64).
  • The first service pack for version 3.5 mitigates this concern by offering a lighter-weight client-only subset of the .NET Framework. Two significant limitations should be noted, though.^[21] Firstly, the client-only subset is only an option on an existing Windows XP SP2 system that currently has no other version of the .NET Framework installed. In all other scenarios, the client-only installer will install the full version of the .NET Framework 3.5 SP1. Secondly, the client-only framework does not have a 64-bit option. However, the 4 release of the .NET Framework Client Profile will be available on all operating systems and all

architectures (excluding Itanium) supported by the full .NET Framework.[22]

• The .NET Framework currently does not provide support for calling Streaming SIMD Extensions (SSE) via managed code. However, Mono has provided support for SIMD Extensions as of version 2.2 within the Mono.Simd namespace; Mono's lead developer Miguel de Icaza has expressed hope that this SIMD support will be adopted by the CLR ECMA standard.^[23] 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 simulated in software.
• While the standards that make up .NET are inherently cross platform, Microsoft's full implementation of .NET is only supported on Windows. Microsoft does provide limited .NET subsets for other platforms such as XNA for Windows, Xbox 360 and Windows Phone 7, Silverlight for Windows and Mac OS X. Alternative implementations of the CLR, base class libraries, and compilers also exist (sometimes from other vendors). While all of these implementations are based on the same standards, they are still different implementations with varying levels of completeness in comparison to the full .NET version Microsoft ships for Windows and are on occasion incompatible.^{[citation needed]}

public class Class1 {

   public SqlConnection Con;
   public SqlCommand cmd;
   public SqlDataAdapter sda;
   public DataTable Dt;
   public Class1()
   {
       string s = 
       Con = new SqlConnection(s);
    }
   public DataTable select_query(string s)
   {
       sda = new SqlDataAdapter(s, Con);
       Dt = new DataTable();
       sda.Fill(Dt);
       return (Dt);
   }
   public void insert_query(string s)
   {
       Con.Open();
       cmd = new SqlCommand(s, Con);
       cmd.ExecuteNonQuery();
       Con.Close();
   }
   public void delete_query(string s)
   {
       Con.Open();
       cmd = new SqlCommand(s, Con);
       cmd.ExecuteNonQuery();
       Con.Close();
   }
   public void update_query(string s)
   {
       Con.Open();
       cmd = new SqlCommand(s, Con);
       cmd.ExecuteNonQuery();
       Con.Close();
   }   

}

Alternative implementations

The Microsoft .NET Framework is the predominant implementation of .NET technologies. Other implementations for parts of the framework exist. Although the runtime engine is described by an ECMA/ISO specification, other implementations 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 document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights."^[24] It is more difficult to develop alternatives to the base class library (BCL), which is not described by an open standard and may be subject to copyright restrictions. Additionally, parts of the BCL have Windows-specific functionality and behavior, so implementation on non-Windows platforms can be problematic.

Some alternative implementations of parts of the framework are listed here.

• Microsoft's .NET Micro Framework is a .NET platform for extremely resource-constrained devices. Suman includes a small version of the .NET CLR and supports development in C# (though some developers were able to use VB.NET^[25], albeit with an amount of hacking, and with limited functionalities) and debugging (in an emulator or on hardware), both using Microsoft Visual Studio. It also features a subset of the .NET base class libraries (about 70 classes with about 420 methods), a GUI framework loosely based on Windows Presentation Foundation, and additional libraries specific to embedded applications.
• Mono is an up-to-date implementation of the CLI and the .NET Base Class Library (BCL), and provides additional functionality. It is dual-licensed under free software and proprietary software 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 implementation of the Common Language Infrastructure (CLI), portions of the .NET Base Class Library (BCL), and a C# compiler. It supports a variety of CPUs and operating systems.
• Microsoft's Shared Source Common Language Infrastructure is a non free implementation of the CLR component of the .NET Framework. 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 the .NET Framework.
• CrossNet is an implementation of the CLI and portions of the .NET Base Class Library (BCL). It is free software using the open source MIT License. As of September 2011, it seems that CrossNet development is not active since October 2007.

References

1. ^ ^{a b} Scott Guthrie (3 October 2007). "Releasing the Source Code for the NET Framework". http://weblogs.asp.net/scottgu/archive/2007/10/03/releasing-the-source-code-for-the-net-framework-libraries.aspx. Retrieved 15 September 2010. 
2. ^ "Framework Versions". http://ben.skyiv.com/clrversion.html. 
3. ^ Microsoft. "Microsoft .NET Framework 3.5 Administrator Deployment Guide". http://msdn.microsoft.com/library/cc160717.aspx. Retrieved 26 June 2008. 
4. ^ ".NET Framework Service Pack 2". http://www.microsoft.com/downloads/en/details.aspx?FamilyID=75b0bc1d-c26c-4bac-ac68-2b4d431cabb5&displaylang=en. Retrieved 2011-05-04. "Windows XP Tablet Edition and Windows XP Media Center Edition already contain .NET Framework 1.0 Service Pack 2." 
5. ^ "Scott Guthrie: Silverlight and the Cross-Platform CLR". Channel 9. 30 April 2007. http://channel9.msdn.com/shows/Going+Deep/Scott-Guthrie-Silverlight-and-the-Cross-Platform-CLR. 
6. ^ "ECMA 335 - Standard ECMA-335 Common Language Infrastructure (CLI)". ECMA. 1 June 2006. http://www.ecma-international.org/publications/standards/Ecma-335.htm. Retrieved 1 June 2008. 
7. ^ ISO/IEC 23271:2006
8. ^ "Technical Report TR/84 Common Language Infrastructure (CLI) - Information Derived from Partition IV XML File". ECMA. 1 June 2006. http://www.ecma-international.org/publications/techreports/E-TR-084.htm. 
9. ^ "ECMA-334 C# Language Specification". ECMA. 1 June 2006. http://www.ecma-international.org/publications/standards/Ecma-334.htm. 
10. ^ "Standard ECMA-372 C++/CLI Language Specification". ECMA. 1 December 2005. http://www.ecma-international.org/publications/standards/Ecma-372.htm. 
11. ^ ^{a b} "Base Class Library". http://msdn.microsoft.com/netframework/aa569603.aspx. Retrieved 1 June 2008. 
12. ^ ^{a b c} "Garbage Collection: Automatic Memory Management in the Microsoft .NET Framework". Archived from the original on 3 July 2007. http://web.archive.org/web/20070703083608/http://msdn.microsoft.com/msdnmag/issues/1100/GCI/. Retrieved 1 June 2008. 
13. ^ ^{a b c} "Garbage collection in .NET". http://www.csharphelp.com/archives2/archive297.html. Retrieved 1 June 2008. 
14. ^ ^{a b c d} "Garbage Collection—Part 2: Automatic Memory Management in the Microsoft .NET Framework". Archived from the original on 26 June 2007. http://web.archive.org/web/20070626080134/http://msdn.microsoft.com/msdnmag/issues/1200/GCI2/default.aspx. Retrieved 1 June 2008. 
15. ^ ISO/IEC 23271:2006 - Information technology - Common Language Infrastructure (CLI) Partitions I to VI
16. ^ ISO/IEC 23270:2006 - Information technology - Programming languages - C#
17. ^ "Microsoft's Empty Promise". Free Software Foundation. 16 July 2009. Archived from the original on 5 August 2009. http://www.fsf.org/news/2009-07-mscp-mono. Retrieved 3 August 2009. "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" 
18. ^ "Reverse Engineering Risk Assessment". http://www.preemptive.com/images/documentation/Reverse_Engineering_Risk_Assessment.pdf. 
19. ^ Gartner, Inc. as reported in "Hype Cycle for Cyberthreats, 2006", September 2006, Neil MacDonald; Amrit Williams, et al.
20. ^ Dotfuscator Community Edition 4.0
21. ^ .NET Framework Client Profile Deployment Scenarios
22. ^ [http://blogs.msdn.com/jgoldb/archive/2009/05/27/net-framework-4-client-profile-introduction.aspx "'.NET Framework 4 Client Profile - Introduction'"]. Archived from the original on 2009-10-04. http://blogs.msdn.com/jgoldb/archive/2009/05/27/net-framework-4-client-profile-introduction.aspx. Retrieved 2009-10-02. 
23. ^ Mono's SIMD Support: Making Mono safe for Gaming
24. ^ ISO 9001:2008, Foreword
25. ^ http://www.christec.co.nz/blog/archives/317

External links

• .NET Framework Developer Center
• .NET Framework 3.5 (MSDN)
• .NET Framework 4.0 (MSDN)