Common Language Infrastructure Explained

Common Language Infrastructure
Status:Published
Version:Sixth edition
Organization:Developed by: Microsoft, Hewlett-Packard, Intel, and others
Standardized by: Ecma, ISO/IEC
Abbreviation:CLI
Domain:Common Language (Cross-platform)
Website:,
Long Name:ISO/IEC 23271:2012(E)
First Published: (Ecma) and (ISO/IEC)
Committee:ISO/IEC JTC 1/SC 22
License:RAND

The Common Language Infrastructure (CLI) is an open specification and technical standard originally developed by Microsoft and standardized by ISO/IEC (ISO/IEC 23271) and Ecma International (ECMA 335)[1] [2] that describes executable code and a runtime environment that allows multiple high-level languages to be used on different computer platforms without being rewritten for specific architectures. This implies it is platform agnostic. The .NET Framework, .NET and Mono are implementations of the CLI.The metadata format is also used to specify the API definitions exposed by the Windows Runtime.[3] [4]

Overview

Among other things, the CLI specification describes the following five aspects:

The Common Type System (CTS)
  • A set of data types and operations that are shared by all CTS-compliant programming languages.
    The Metadata
  • Information about program structure is language-agnostic, so that it can be referenced between languages and tools, making it easy to work with code written in a language the developer is not using.
    The Common Language Specification (CLS)
  • The CLS, a subset of the CTS, are rules to which components developed with/for the supported languages must adhere.
  • They apply to consumers (developers who are programmatically accessing a component that is CLS-compliant), frameworks (developers who are using a language compiler to create CLS-compliant libraries), and extenders (developers who are creating a tool such as a language compiler or a code parser that creates CLS-compliant components).
    The Virtual Execution System (VES)
  • The VES loads and executes CLI-compatible programs, using the metadata to combine separately generated pieces of code at runtime.
  • All compatible languages compile to Common Intermediate Language (CIL), which is an intermediate language that is abstracted from the platform hardware. When the code is executed, the platform-specific VES will compile the CIL to the machine language according to the specific hardware and operating system.
  • In the CLI standard initially developed by Microsoft, the VES is implemented by the Common Language Runtime (CLR).
    The Standard Libraries
  • A set of libraries providing many common functions, such as file reading and writing. Their core is the Base Class Library (BCL).

    Standardization and licensing

    In August 2000, Microsoft, Hewlett-Packard, Intel, and others worked to standardize CLI. By December 2001, it was ratified by the Ecma, with ISO/IEC standardization following in April 2003.

    Microsoft and its partners hold patents for CLI. Ecma and ISO/IEC require that all patents essential to implementation be made available under "reasonable and non-discriminatory (RAND) terms." It is common for RAND licensing to require some royalty payment, which could be a cause for concern with Mono. As of January 2013, neither Microsoft nor its partners have identified any patents essential to CLI implementations subject to RAND terms.

    As of July 2009,[5] Microsoft added C# and CLI to the list of specifications that the Microsoft Community Promise applies to,[6] so anyone can safely implement specified editions of the standards without fearing a patent lawsuit from Microsoft. To implement the CLI standard requires conformance to one of the supported and defined profiles of the standard, the minimum of which is the kernel profile. The kernel profile is actually a very small set of types to support in comparison to the well known core library of default .NET installations. However, the conformance clause of the CLI allows for extending the supported profile by adding new methods and types to classes, as well as deriving from new namespaces. But it does not allow for adding new members to interfaces. This means that the features of the CLI can be used and extended, as long as the conforming profile implementation does not change the behavior of a program intended to run on that profile, while allowing for unspecified behavior from programs written specifically for that implementation.

    In 2012, Ecma and ISO/IEC published the new edition of the CLI standard.[1] [2]

    Implementations

    See also

    References

    Notes and References

    1. Web site: ISO/IEC 23271:2012 - Information technology -- Common Language Infrastructure (CLI) . ISO . live . https://web.archive.org/web/20230702003946/https://www.iso.org/standard/58046.html . Jul 2, 2023 .
    2. Web site: ECMA-335 . 6th edition . June 2012 . ECMA International . live . https://web.archive.org/web/20231016101943/https://www.ecma-international.org/publications-and-standards/standards/ecma-335/ . Oct 16, 2023 .
    3. Web site: Introduction to Advanced Windows Store App Development using HTML5 and JavaScript . Microsoft Press Store . Oct 15, 2013 . live . https://web.archive.org/web/20230330075408/https://www.microsoftpressstore.com/articles/article.aspx?p=2199428&seqNum=3 . Mar 30, 2023 .
    4. Web site: WinRT demystified . Miguel . de Icaza . 15 Sep 2011 . live . https://web.archive.org/web/20231130221232/https://tirania.org/blog/archive/2011/Sep-15.html . Nov 30, 2023 .
    5. Web site: The Ecma C# and CLI Standards . Port 25. Peter . Galli. 2009-07-06. September 26, 2009. https://web.archive.org/web/20090709232640/http://port25.technet.com/archive/2009/07/06/the-ecma-c-and-cli-standards.aspx. July 9, 2009. dead.
    6. Web site: v-alje . [MS-DEVCENTLP]

      Microsoft Community Promise ]

      . 2023-05-01 . Microsoft Learn . March 16, 2023 . en-us.

    This article is licensed under the GNU Free Documentation License. It uses material from the Wikipedia article "Common Language Infrastructure".

    Except where otherwise indicated, Everything.Explained.Today is © Copyright 2009-2024, A B Cryer, All Rights Reserved. Cookie policy.