INCITS/ISO/IEC 23271 : 2013

1 Scope
2 Conformance
3 References
4 Conventions
   4.1 Organization
   4.2 Informative Text
   4.3 Hyperlinks
5 Glossary
6 Overview of the Common Language Infrastructure
   6.1 Relationship to Type Safety
   6.2 Relationship to Managed Metadata-driven Execution
7 Common Language Specification (CLS)
   7.1 Introduction
   7.2 Views of CLS Compliance
   7.3 CLS Compliance
8 Common Type System
   8.1 Relationship to Object-Oriented Programming
   8.2 Values and Types
   8.3 Locations
   8.4 Type Members
   8.5 Naming
   8.6 Contracts
   8.7 Assignment Compatibility
   8.8 Type Safety and Verification
   8.9 Type Definers
   8.10 Member Inheritance
   8.11 Member Definitions
9 Metadata
   9.1 Components and Assemblies
   9.2 Accessing Metadata
   9.3 Unmanaged Code
   9.4 Method Implementation Metadata
   9.5 Class Layout
   9.6 Assemblies: Name Scopes for Types
   9.7 Metadata Extensibility
   9.8 Globals, Imports, and Exports
   9.9 Scoped Statics
10 Name and Type Rules for the Common Language Specification
   10.1 Identifiers
   10.2 Overloading
   10.3 Operator Overloading
   10.4 Naming Patterns
   10.5 Exceptions
   10.6 Custom Attributes
11 Collected CLS Rules
12 Virtual Execution System
   12.1 Supported Data Types
   12.2 Module Information
   12.3 Machine State
   12.4 Control Flow
   12.5 Proxies and Remoting
   12.6 Memory Model and Optimizations
13 Index

Defines the Common Language Infrastructure (CLI) in which applications written in multiple high-level languages may be executed in different system environments without the need to rewrite the applications to take into consideration the unique characteristics of those environments.