.NET Common Language Runtime

.NET Common Language Runtime
Name	.NET Common Language Runtime
Developer	Microsoft
Released	13 February 2002
Programming language	C++, C#
Operating system	Microsoft Windows, Linux, macOS
Platform	.NET Framework, .NET
Genre	Runtime system
License	MIT License

.NET Common Language Runtime. The Common Language Runtime (CLR) is the foundational execution engine of the .NET Framework and its cross-platform successor, .NET. Developed by Microsoft, it provides a managed environment for running applications written in various languages like C# and Visual Basic .NET. The CLR handles critical services such as memory management, type safety, and exception handling, enabling developers to focus on application logic.

Overview

The CLR serves as the virtual machine component within the .NET Framework architecture, abstracting the underlying operating system and computer hardware. It executes Common Intermediate Language (CIL) code, which is generated by compilers for languages targeting the .NET platform. Key to its design is the Common Type System (CTS), which ensures language interoperability by defining a universal set of data types and rules. This runtime environment is central to Microsoft's strategy for building secure and reliable Windows applications, and it has since evolved to support Linux and macOS through .NET Core and .NET 5.

Architecture

The architecture of the CLR is built around several core components that work together to manage code execution. The Class Loader is responsible for loading assemblies and their contained types into the runtime. The Just-In-Time (JIT) compiler translates Common Intermediate Language instructions into native machine code for the host processor. The Common Type System and Common Language Specification (CLS) provide the foundational rules for type definition and cross-language integration. Other critical subsystems include the Thread Pool for managing concurrency and the Exception Handling mechanism for managing runtime errors.

Managed execution

Managed execution refers to the process where the CLR controls the lifecycle and execution of .NET code. When an application starts, the CLR loads the required assemblies and uses the JIT compiler to convert Common Intermediate Language into optimized x86, x64, or ARM instructions. The runtime enforces code access security policies and validates code for type safety and memory safety before execution. This managed environment contrasts with unmanaged code like that written in C++, which does not receive these automatic services from the CLR.

Memory management

A cornerstone of the CLR is its automatic memory management, primarily implemented through a tracing garbage collection system. The Garbage Collector (GC) automatically allocates objects on the managed heap and reclaims memory from objects no longer in use, preventing memory leaks. The GC employs a generational garbage collection strategy, segregating objects into Generation 0, Generation 1, and Generation 2 based on lifespan to optimize performance. This system relieves developers from manual memory management tasks common in languages like C++ and is a key feature for building robust enterprise software.

Security model

The CLR implements a robust security model designed to protect systems and data. Its code access security (CAS) system, prominent in the .NET Framework 2.0, evaluates assembly evidence like its digital signature or URL to grant permissions. The runtime also enforces role-based security integrated with Windows authentication systems like Active Directory. With the evolution of the platform, emphasis has shifted towards security transparency and sandboxing models, particularly in .NET Core. These mechanisms help mitigate threats from malware and ensure application isolation.

Interoperability

The CLR provides extensive interoperability features to allow managed code to interact with existing unmanaged components. Platform Invocation Services (P/Invoke) enables calls to functions in native DLLs, such as the Windows API. COM Interop facilitates communication with Component Object Model components, crucial for integrating with legacy Microsoft Office applications or Internet Explorer. Furthermore, the runtime supports C++/CLI as a language for writing mixed-mode assemblies that bridge managed and unmanaged code, easing migration from technologies like Microsoft Foundation Class Library.

Version history

The CLR has evolved significantly since its initial release with the .NET Framework 1.0 in 2002. Major updates included the .NET Framework 2.0 (2005), which introduced a revised generational garbage collection and expanded generic programming support. The .NET Framework 4.0 (2010) brought a new CLR 4 with features like the Dynamic Language Runtime. A pivotal shift occurred with the open-source .NET Core project, leading to a cross-platform CLR. This culminated in the unified .NET 5 (2020) and subsequent releases, which merged .NET Framework, .NET Core, and Xamarin into a single modern runtime.

Category:.NET Framework Category:Runtime systems Category:Microsoft application programming interfaces Category:Virtual machines