ParadigmMulti-paradigm: structured, imperative, object-oriented, event-driven, task-driven, functional, generic, reflective, concurrent
Designed byAnders Hejlsberg (Microsoft)
DeveloperMads Torgersen (Microsoft)
First appeared2000; 24 years ago (2000)[1]
Stable release
12.0[2] Edit this on Wikidata / 14 November 2023; 4 months ago (14 November 2023)
Typing disciplineStatic, dynamic,[3] strong, safe, nominative, partly inferred
Memory managementautomatic memory management
PlatformCommon Language Infrastructure
Filename extensions.cs, .csx
Major implementations
Visual C#, .NET, Mono, Universal Windows Platform
Discontinued: .NET Framework, DotGNU
, Polyphonic C#, Enhanced C#
Influenced by
C++,[6] , Eiffel, F#,[a] Haskell, Scala, Icon, J#, J++, Java,[6] ML, Modula-3, Object Pascal,[7] VB
Chapel,[8] Clojure,[9] Crystal,[10] D, J#, Dart,[11] F#, Hack, Java,[12][13] Kotlin, Nemerle, Oxygene, Rust,[14] Swift,[15] Vala, TypeScript

C# (/ˌs ˈʃɑːrp/ see SHARP)[b] is a general-purpose high-level programming language supporting multiple paradigms. C# encompasses static typing,[16]: 4  strong typing, lexically scoped, imperative, declarative, functional, generic,[16]: 22  object-oriented (class-based), and component-oriented programming disciplines.[17]

The C# programming language was designed by Anders Hejlsberg from Microsoft in 2000 and was later approved as an international standard by Ecma (ECMA-334) in 2002 and ISO/IEC (ISO/IEC 23270 and 20619[c]) in 2003. Microsoft introduced C# along with .NET Framework and Visual Studio, both of which were closed-source. At the time, Microsoft had no open-source products. Four years later, in 2004, a free and open-source project called Mono began, providing a cross-platform compiler and runtime environment for the C# programming language. A decade later, Microsoft released Visual Studio Code (code editor), Roslyn (compiler), and the unified .NET platform (software framework), all of which support C# and are free, open-source, and cross-platform. Mono also joined Microsoft but was not merged into .NET.

As of November 2023, the most recent stable version of the language is C# 12.0, which was released in 2023 in .NET 8.0.[18][19]

Design goals

The Ecma standard lists these design goals for C#:[17]


During the development of the .NET Framework, the class libraries were originally written using a managed code compiler system called "Simple Managed C" (SMC).[22][23] In January 1999, Anders Hejlsberg formed a team to build a new language at the time called Cool, which stood for "C-like Object Oriented Language".[24] Microsoft had considered keeping the name "Cool" as the final name of the language, but chose not to do so for trademark reasons. By the time the .NET project was publicly announced at the July 2000 Professional Developers Conference, the language had been renamed C#, and the class libraries and ASP.NET runtime had been ported to C#.

Hejlsberg is C#'s principal designer and lead architect at Microsoft, and was previously involved with the design of Turbo Pascal, Embarcadero Delphi (formerly CodeGear Delphi, Inprise Delphi and Borland Delphi), and Visual J++. In interviews and technical papers he has stated that flaws[25] in most major programming languages (e.g. C++, Java, Delphi, and Smalltalk) drove the fundamentals of the Common Language Runtime (CLR), which, in turn, drove the design of the C# language itself.

James Gosling, who created the Java programming language in 1994, and Bill Joy, a co-founder of Sun Microsystems, the originator of Java, called C# an "imitation" of Java; Gosling further said that "[C# is] sort of Java with reliability, productivity and security deleted."[26][27] In July 2000, Hejlsberg said that C# is "not a Java clone" and is "much closer to C++" in its design.[28]

Since the release of C# 2.0 in November 2005, the C# and Java languages have evolved on increasingly divergent trajectories, becoming two quite different languages. One of the first major departures came with the addition of generics to both languages, with vastly different implementations. C# makes use of reification to provide "first-class" generic objects that can be used like any other class, with code generation performed at class-load time.[29] Furthermore, C# has added several major features to accommodate functional-style programming, culminating in the LINQ extensions released with C# 3.0 and its supporting framework of lambda expressions, extension methods, and anonymous types.[30] These features enable C# programmers to use functional programming techniques, such as closures, when it is advantageous to their application. The LINQ extensions and the functional imports help developers reduce the amount of boilerplate code that is included in common tasks like querying a database, parsing an xml file, or searching through a data structure, shifting the emphasis onto the actual program logic to help improve readability and maintainability.[31]

C# used to have a mascot called Andy (named after Anders Hejlsberg). It was retired on January 29, 2004.[32]

C# was originally submitted to the ISO/IEC JTC 1 subcommittee SC 22 for review,[33] under ISO/IEC 23270:2003,[34] was withdrawn and was then approved under ISO/IEC 23270:2006.[35] The 23270:2006 is withdrawn under 23270:2018 and approved with this version.[36]


Microsoft first used the name C# in 1988 for a variant of the C language designed for incremental compilation.[37] That project was not completed, and the name was later reused.

C-sharp musical note

The name "C sharp" was inspired by the musical notation whereby a sharp symbol indicates that the written note should be made a semitone higher in pitch.[38] This is similar to the language name of C++, where "++" indicates that a variable should be incremented by 1 after being evaluated. The sharp symbol also resembles a ligature of four "+" symbols (in a two-by-two grid), further implying that the language is an increment of C++.[39]

Due to technical limitations of display (standard fonts, browsers, etc.) and the fact that the sharp symbol (U+266F MUSIC SHARP SIGN (♯)) is not present on most keyboard layouts, the number sign (U+0023 # NUMBER SIGN (#)) was chosen to approximate the sharp symbol in the written name of the programming language.[40] This convention is reflected in the ECMA-334 C# Language Specification.[17]

The "sharp" suffix has been used by a number of other .NET languages that are variants of existing languages, including J# (a .NET language also designed by Microsoft that is derived from Java 1.1), A# (from Ada), and the functional programming language F#.[41] The original implementation of Eiffel for .NET was called Eiffel#,[42] a name retired since the full Eiffel language is now supported. The suffix has also been used for libraries, such as Gtk# (a .NET wrapper for GTK and other GNOME libraries) and Cocoa# (a wrapper for Cocoa).


Version Language specification Date .NET Visual Studio
Ecma ISO/IEC Microsoft
C# 1.0 ECMA-334:2003, December 2002 ISO/IEC 23270:2003, April 2003 January 2002 January 2002 .NET Framework 1.0 Visual Studio .NET 2002
C# 1.1
C# 1.2
October 2003 April 2003 Visual Studio .NET 2003
C# 2.0[43] ECMA-334:2006, June 2006 ISO/IEC 23270:2006, September 2006 September 2005[d] November 2005 Visual Studio 2005
Visual Studio 2008
C# 3.0[44] None August 2007 November 2007
Visual Studio 2008
C# 4.0[46] April 2010 April 2010 Visual Studio 2010
C# 5.0[47] ECMA-334:2017, December 2017 ISO/IEC 23270:2018, December 2018 June 2013 August 2012 Visual Studio 2012
Visual Studio 2013
C# 6.0[48] ECMA-334:2022, June 2022 None Draft July 2015
Visual Studio 2015
C# 7.0[49][50] ECMA-334:2023, December 2023 ISO/IEC 20619:2023, September 2023 Specification proposal March 2017 Visual Studio 2017 version 15.0[51]
C# 7.1[52] None Specification proposal August 2017
  • .NET Core 2.0
Visual Studio 2017 version 15.3[53]
C# 7.2[54] Specification proposal November 2017 Visual Studio 2017 version 15.5[55]
C# 7.3[56] Specification proposal Archived March 7, 2021, at the Wayback Machine May 2018
Visual Studio 2017 version 15.7[57]
C# 8.0[58] Specification proposal September 2019
  • .NET Core 3.0
  • .NET Core 3.1
Visual Studio 2019 version 16.3[59]
C# 9.0[60] Specification proposal November 2020
  • .NET 5.0
Visual Studio 2019 version 16.8[61]
C# 10.0[62] Specification proposal November 2021
  • .NET 6.0
Visual Studio 2022 version 17.0[63]
C# 11.0[64] Specification proposal November 2022
  • .NET 7.0
Visual Studio 2022 version 17.4[65]
C# 12.0[66] Specification proposal November 2023
  • .NET 8.0
Visual Studio 2022 version 17.8[67]


Main article: C# syntax

See also: Syntax (programming languages)

The core syntax of the C# language is similar to that of other C-style languages such as C, C++ and Java, particularly:

Distinguishing features

See also: Comparison of C# and Java

Some notable features of C# that distinguish it from C, C++, and Java where noted, are:


By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI).[68] Most of its intrinsic types correspond to value-types implemented by the CLI framework. However, the language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime, or generate Common Intermediate Language (CIL), or generate any other specific format. Some C# compilers can also generate machine code like traditional compilers of C++ or Fortran.[69][70]


C# supports strongly, implicitly typed variable declarations with the keyword var,[16]: 470  and implicitly typed arrays with the keyword new[] followed by a collection initializer.[16]: 80 [20]: 58 

C# supports a strict Boolean data type, bool. Statements that take conditions, such as while and if, require an expression of a type that implements the true operator, such as the Boolean type. While C++ also has a Boolean type, it can be freely converted to and from integers, and expressions such as if (a) require only that a is convertible to bool, allowing a to be an int, or a pointer. C# disallows this "integer meaning true or false" approach, on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of programming mistakes such as if (a = b) (use of assignment = instead of equality ==).

C# is more type safe than C++. The only implicit conversions by default are those that are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. No implicit conversions occur between Booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion operators, which are both implicit by default.

C# has explicit support for covariance and contravariance in generic types,[16]: 144 [20]: 23  unlike C++ which has some degree of support for contravariance simply through the semantics of return types on virtual methods.

Enumeration members are placed in their own scope.

The C# language does not allow for global variables or functions. All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions.

Local variables cannot shadow variables of the enclosing block, unlike C and C++.


Metaprogramming can be achieved in several ways:

Methods and functions

A method in C# is a member of a class that can be invoked as a function (a sequence of instructions), rather than the mere value-holding capability of a class property. As in other syntactically similar languages, such as C++ and ANSI C, the signature of a method is a declaration comprising in order: any optional accessibility keywords (such as private), the explicit specification of its return type (such as int, or the keyword void if no value is returned), the name of the method, and finally, a parenthesized sequence of comma-separated parameter specifications, each consisting of a parameter's type, its formal name and optionally, a default value to be used whenever none is provided. Certain specific kinds of methods, such as those that simply get or set a class property by return value or assignment, do not require a full signature, but in the general case, the definition of a class includes the full signature declaration of its methods.

Like C++, and unlike Java, C# programmers must use the scope modifier keyword virtual to allow methods to be overridden by subclasses.[75]

Extension methods in C# allow programmers to use static methods as if they were methods from a class's method table, allowing programmers to add methods to an object that they feel should exist on that object and its derivatives.[16]: 103–105 [20]: 202–203 

The type dynamic allows for run-time method binding, allowing for JavaScript-like method calls and run-time object composition.[16]: 114–118 

C# has support for strongly-typed function pointers via the keyword delegate. Like the Qt framework's pseudo-C++ signal and slot, C# has semantics specifically surrounding publish-subscribe style events, though C# uses delegates to do so.

C# offers Java-like synchronized method calls, via the attribute [MethodImpl(MethodImplOptions.Synchronized)], and has support for mutually-exclusive locks via the keyword lock.


C# supports classes with properties. The properties can be simple accessor functions with a backing field, or implement getter and setter functions.

Since C# 3.0 the syntactic sugar of auto-implemented properties is available,[76] where the accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class.


A C# namespace provides the same level of code isolation as a Java package or a C++ namespace, with very similar rules and features to a package. Namespaces can be imported with the "using" syntax.[77]

Memory access

In C#, memory address pointers can only be used within blocks specifically marked as unsafe,[78] and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object (one that has been garbage collected), or to a random block of memory. An unsafe pointer can point to an instance of an unmanaged value type that does not contain any references to objects subject to garbage collections such as class instances, arrays or strings. Code that is not marked as unsafe can still store and manipulate pointers through the System.IntPtr type, but it cannot dereference them.

Managed memory cannot be explicitly freed; instead, it is automatically garbage collected. Garbage collection addresses the problem of memory leaks by freeing the programmer of responsibility for releasing memory that is no longer needed in most cases. Code that retains references to objects longer than is required can still experience higher memory usage than necessary, however once the final reference to an object is released the memory is available for garbage collection.


A range of standard exceptions are available to programmers. Methods in standard libraries regularly throw system exceptions in some circumstances and the range of exceptions thrown is normally documented. Custom exception classes can be defined for classes allowing handling to be put in place for particular circumstances as needed.[79]

Checked exceptions are not present in C# (in contrast to Java). This has been a conscious decision based on the issues of scalability and versionability.[80]


Unlike C++, C# does not support multiple inheritance, although a class can implement any number of "interfaces" (fully abstract classes). This was a design decision by the language's lead architect to avoid complications and to simplify architectural requirements throughout CLI.

When implementing multiple interfaces that contain a method with the same name and taking parameters of the same type in the same order (i.e. the same signature), similar to Java, C# allows both a single method to cover all interfaces and if necessary specific methods for each interface.

However, unlike Java, C# supports operator overloading.[81]

Language Integrated Query (LINQ)

C# has the ability to utilize LINQ through the .NET Framework. A developer can query a variety of data sources, provided IEnumerable<T> interface is implemented on the object. This includes XML documents, an ADO.NET dataset, and SQL databases.[82]

Using LINQ in C# brings advantages like IntelliSense support, strong filtering capabilities, type safety with compile error checking ability, and consistency for querying data over a variety of sources.[83] There are several different language structures that can be utilized with C# and LINQ and they are query expressions, lambda expressions, anonymous types, implicitly typed variables, extension methods, and object initializers.[84]

LINQ has two syntaxes: query syntax and method syntax. However, the compiler always converts the query syntax to method syntax at compile time.[85]

using System.Linq;

var numbers = new int[] { 5, 10, 8, 3, 6, 12 };

// Query syntax (SELECT num FROM numbers WHERE num % 2 = 0 ORDER BY num)
var numQuery1 =
        from num in numbers
        where num % 2 == 0
        orderby num
        select num;

// Method syntax
var numQuery2 = 
        .Where(num => num % 2 == 0)
        .OrderBy(n => n);

Functional programming

Though primarily an imperative language, C# always adds functional features over time,[86][87] for example:

Common type system

C# has a unified type system. This unified type system is called Common Type System (CTS).[94]: Part 2, Chapter 4: The Type System 

A unified type system implies that all types, including primitives such as integers, are subclasses of the System.Object class. For example, every type inherits a ToString() method.

Categories of data types

CTS separates data types into two categories:[94]

  1. Reference types
  2. Value types

Instances of value types neither have referential identity nor referential comparison semantics. Equality and inequality comparisons for value types compare the actual data values within the instances, unless the corresponding operators are overloaded. Value types are derived from System.ValueType, always have a default value, and can always be created and copied. Some other limitations on value types are that they cannot derive from each other (but can implement interfaces) and cannot have an explicit default (parameterless) constructor because they already have an implicit one which initializes all contained data to the type-dependent default value (0, null, or alike). Examples of value types are all primitive types, such as int (a signed 32-bit integer), float (a 32-bit IEEE floating-point number), char (a 16-bit Unicode code unit), and System.DateTime (identifies a specific point in time with nanosecond precision). Other examples are enum (enumerations) and struct (user defined structures).

In contrast, reference types have the notion of referential identity, meaning that each instance of a reference type is inherently distinct from every other instance, even if the data within both instances is the same. This is reflected in default equality and inequality comparisons for reference types, which test for referential rather than structural equality, unless the corresponding operators are overloaded (such as the case for System.String). Some operations are not always possible, such as creating an instance of a reference type, copying an existing instance, or performing a value comparison on two existing instances. Though specific reference types can provide such services by exposing a public constructor or implementing a corresponding interface (such as ICloneable or IComparable). Examples of reference types are object (the ultimate base class for all other C# classes), System.String (a string of Unicode characters), and System.Array (a base class for all C# arrays).

Both type categories are extensible with user-defined types.

Boxing and unboxing

Boxing is the operation of converting a value-type object into a value of a corresponding reference type.[94] Boxing in C# is implicit.

Unboxing is the operation of converting a value of a reference type (previously boxed) into a value of a value type.[94] Unboxing in C# requires an explicit type cast. A boxed object of type T can only be unboxed to a T (or a nullable T).[95]


int foo = 42;         // Value type.
object bar = foo;     // foo is boxed to bar.
int foo2 = (int)bar;  // Unboxed back to value type.


The C# specification details a minimum set of types and class libraries that the compiler expects to have available. In practice, C# is most often used with some implementation of the Common Language Infrastructure (CLI), which is standardized as ECMA-335 Common Language Infrastructure (CLI).

In addition to the standard CLI specifications, there are many commercial and community class libraries that build on top of the .NET framework libraries to provide additional functionality.[96]

C# can make calls to any library included in the List of .NET libraries and frameworks.


Hello World

The following is a very simple C# program, a version of the classic "Hello world" example using the top-level statements feature introduced in C# 9:[97]

using System;

Console.WriteLine("Hello, world!");

For code written as C# 8 or lower, the entry point logic of a program must be written in a Main method inside a type:

using System;

class Program
    static void Main()
        Console.WriteLine("Hello, world!");

This code will display this text in the console window:

Hello, world!

Each line has a purpose:

using System;

The above line imports all types in the System namespace. For example, the Console class used later in the source code is defined in the System namespace, meaning it can be used without supplying the full name of the type (which includes the namespace).

// A version of the classic "Hello World" program

This line is a comment; it describes and documents the code for the programmer(s).

class Program

Above is a class definition for the Program class. Everything that follows between the pair of braces describes that class.


The curly brackets demarcate the boundaries of a code block. In this first instance, they are marking the start and end of the Program class.

static void Main()

This declares the class member method where the program begins execution. The .NET runtime calls the Main method. Unlike in Java, the Main method does not need the public keyword, which tells the compiler that the method can be called from anywhere by any class.[98] Writing static void Main(string[] args) is equivalent to writing private static void Main(string[] args). The static keyword makes the method accessible without an instance of Program. Each console application's Main entry point must be declared static otherwise the program would require an instance of Program, but any instance would require a program. To avoid that irresolvable circular dependency, C# compilers processing console applications (like that above) report an error if there is no static Main method. The void keyword declares that Main has no return value. (Note, however, that short programs can be written using Top Level Statements introduced in C# 9, as mentioned earlier.)

Console.WriteLine("Hello, world!");

This line writes the output. Console is a static class in the System namespace. It provides an interface to the standard input, output, and error streams for console applications. The program calls the Console method WriteLine, which displays on the console a line with the argument, the string "Hello, world!".


A Windows GUI example:

using System;
using System.Windows.Forms;

class Program
    static void Main()
        MessageBox.Show("Hello, World!");
        Console.WriteLine("Is almost the same argument!");

This example is similar to the previous example, except that it generates a dialog box that contains the message "Hello, World!" instead of writing it to the console.


Another useful library is the System.Drawing library, which is used to programmatically draw images. For example:

using System;
using System.Drawing;

public class Example
    public static Image img;

    static void Main()
        img = Image.FromFile("Image.png");

This will create an image that is identical to that stored in "Image.png".

Standardization and licensing

In August 2001, Microsoft, Hewlett-Packard and Intel co-sponsored the submission of specifications for C# as well as the Common Language Infrastructure (CLI) to the standards organization Ecma International. In December 2001, ECMA released ECMA-334 C# Language Specification. C# became an ISO/IEC standard in 2003 (ISO/IEC 23270:2003 - Information technology — Programming languages — C#). ECMA had previously adopted equivalent specifications as the 2nd edition of C#, in December 2002. In June 2005, ECMA approved edition 3 of the C# specification, and updated ECMA-334. Additions included partial classes, anonymous methods, nullable types, and generics (somewhat similar to C++ templates). In July 2005, ECMA submitted to ISO/IEC JTC 1/SC 22, via the latter's Fast-Track process, the standards and related TRs. This process usually takes 6–9 months.

The C# language definition and the CLI are standardized under ISO/IEC and Ecma standards that provide reasonable and non-discriminatory licensing protection from patent claims.

Microsoft initially agreed not to sue open-source developers for violating patents in non-profit projects for the part of the framework that is covered by the Open Specification Promise.[99] Microsoft has also agreed not to enforce patents relating to Novell products against Novell's paying customers[100] with the exception of a list of products that do not explicitly mention C#, .NET or Novell's implementation of .NET (The Mono Project).[101] However, Novell maintained that Mono does not infringe any Microsoft patents.[102] Microsoft also made a specific agreement not to enforce patent rights related to the Moonlight browser plugin, which depends on Mono, provided it is obtained through Novell.[103]

A decade later, Microsoft began developing free, open-source, and cross-platform tooling for C#, namely Visual Studio Code, .NET Core, and Roslyn. Mono joined Microsoft as a project of Xamarin, a Microsoft subsidiary.


Microsoft is leading the development of the open-source reference C# compilers and set of tools. The first compiler, Roslyn, compiles into intermediate language (IL), and the second one, RyuJIT,[104] is a JIT (just-in-time) compiler, which is dynamic and does on-the-fly optimization and compiles the IL into native code for the front-end of the CPU.[105] RyuJIT is open source and written in C++.[106] Roslyn is entirely written in managed code (C#), has been opened up and functionality surfaced as APIs. It is thus enabling developers to create refactoring and diagnostics tools.[4][107] Two branches of official implementation are .NET Framework (closed-source, Windows-only) and .NET Core (open-source, cross-platform); they eventually converged into one open-source implementation: .NET 5.0.[108] At .NET Framework 4.6, a new JIT compiler replaced the former.[104][109]

Other C# compilers (some of which include an implementation of the Common Language Infrastructure and .NET class libraries):

The Unity game engine uses C# as its primary scripting language. The Godot game engine has implemented an optional C# module thanks to a donation of $24,000 from Microsoft.[110]

See also


  1. ^ for async
  2. ^ By convention, a number sign is used for the second character in normal text; in artistic representations, sometimes a true sharp sign is used: C♯. However the ECMA 334 standard states: "The name C# is written as the LATIN CAPITAL LETTER C (U+0043) followed by the NUMBER SIGN # (U+0023)."
  3. ^ Language versions 1.0, 2.0, and 5.0 are available as ISO/IEC 23270. Beginning with version 7.0, the specification is available as ISO/IEC 20619
  4. ^ The Microsoft C# 2.0 specification document only contains the new 2.0 features. For older features, use the 1.2 specification above.


  1. ^ "InfoQ eMag: A Preview of C# 7".
  2. ^ "Announcing C# 12". Retrieved November 18, 2023.
  3. ^ Torgersen, Mads (October 27, 2008). "New features in C# 4.0". Microsoft. Retrieved October 28, 2008.
  4. ^ a b "The Roslyn .NET compiler provides C# and Visual Basic languages with rich code analysis APIs.: dotnet/roslyn". November 13, 2019 – via GitHub.
  5. ^ "CoreCLR is the runtime for .NET Core. It includes the garbage collector, JIT compiler, primitive data types and low-level classes.: dotnet/coreclr". November 13, 2019 – via GitHub.
  6. ^ a b Naugler, David (May 2007). "C# 2.0 for C++ and Java programmer: conference workshop". Journal of Computing Sciences in Colleges. 22 (5). Although C# has been strongly influenced by Java it has also been strongly influenced by C++ and is best viewed as a descendant of both C++ and Java.
  7. ^ Hamilton, Naomi (October 1, 2008). "The A-Z of Programming Languages: C#". Computerworld. Archived from the original on March 24, 2010. Retrieved February 12, 2010. We all stand on the shoulders of giants here and every language builds on what went before it so we owe a lot to C, C++, Java, Delphi, all of these other things that came before us. (Anders Hejlsberg)
  8. ^ "Chapel spec (Acknowledgments)" (PDF). Cray Inc. October 1, 2015. Retrieved January 14, 2016.
  9. ^ "Rich Hickey Q&A by Michael Fogus". Archived from the original on January 11, 2017. Retrieved January 11, 2017.
  10. ^ Borenszweig, Ary (June 14, 2016). "Crystal 0.18.0 released!". It's heavily inspired by Ruby, and other languages (like C#, Go and Python).
  11. ^ "Web Languages and VMs: Fast Code is Always in Fashion. (V8, Dart) - Google I/O 2013". YouTube. Archived from the original on December 21, 2021. Retrieved December 22, 2013.
  12. ^ Java 5.0 added several new language features (the enhanced for loop, autoboxing, varargs and annotations), after they were introduced in the similar (and competing) C# language [1] [2]
  13. ^ Cornelius, Barry (December 1, 2005). "Java 5 catches up with C#". University of Oxford Computing Services. Retrieved June 18, 2014. In my opinion, it is C# that has caused these radical changes to the Java language. (Barry Cornelius)
  14. ^ "Influences - The Rust Reference". The Rust Reference. Retrieved April 18, 2023.
  15. ^ Lattner, Chris (June 3, 2014). "Chris Lattner's Homepage". Chris Lattner. Retrieved May 12, 2020. The Swift language is the product of tireless effort from a team of language experts, documentation gurus, compiler optimization ninjas, and an incredibly important internal dogfooding group who provided feedback to help refine and battle-test ideas. Of course, it also greatly benefited from the experiences hard-won by many other languages in the field, drawing ideas from Objective-C, Rust, Haskell, Ruby, Python, C#, CLU, and far too many others to list.
  16. ^ a b c d e f g Skeet 2019.
  17. ^ a b c C# Language Specification (PDF) (4th ed.). Ecma International. June 2006. Retrieved January 26, 2012.
  18. ^ Dollard, Kathleen (November 14, 2023). "Announcing C# 12". .NET Blog. Retrieved November 18, 2023.
  19. ^ Seth, Gaurav (November 14, 2023). "Announcing .NET 8". .NET Blog. Retrieved November 18, 2023.
  20. ^ a b c d e f Albahari 2022.
  21. ^ "Design Goals of C#". www.java-samples.com. Retrieved October 6, 2021.
  22. ^ Zander, Jason (November 22, 2007). "Couple of Historical Facts". Retrieved February 23, 2009.
  23. ^ "What language was ASP.Net originally written in?". November 28, 2006. Archived from the original on June 24, 2016. Retrieved February 21, 2008.
  24. ^ Hamilton, Naomi (October 1, 2008). "The A-Z of Programming Languages: C#". Computerworld. Archived from the original on May 18, 2019. Retrieved October 1, 2008.
  25. ^ "Details". nilsnaegele.com. Archived from the original on April 7, 2019. Retrieved April 7, 2019.
  26. ^ "Why Microsoft's C# isn't". CNET: CBS Interactive. 2002. Retrieved September 18, 2023.
  27. ^ Bill Joy (February 7, 2002). "Microsoft's blind spot". cnet.com. Retrieved September 18, 2023.
  28. ^ Osborn, John (August 1, 2000). "Deep Inside C#: An Interview with Microsoft Chief Architect Anders Hejlsberg". O'Reilly Media. Retrieved November 14, 2009. ((cite journal)): Cite journal requires |journal= (help)
  29. ^ "Generics (C# Programming Guide)". Microsoft. Retrieved March 21, 2011.
  30. ^ Don Box and Anders Hejlsberg (February 2007). "LINQ: .NET Language-Integrated Query". Microsoft. Retrieved March 21, 2011.
  31. ^ Mercer, Ian (April 15, 2010). "Why functional programming and LINQ is often better than procedural code". abodit.com. Archived from the original on July 11, 2011. Retrieved March 21, 2011.
  32. ^ "Andy Retires". Dan Fernandez's Blog. Blogs.msdn.com. January 29, 2004. Archived from the original on January 19, 2016. Retrieved October 4, 2012.
  33. ^ "Technical committees - JTC 1/SC 22 - Programming languages, their environments and system software interfaces". ISO. Retrieved October 4, 2012.
  34. ^ "ISO/IEC 23270:2003 - Information technology - C# Language Specification". Iso.org. August 23, 2006. Archived from the original on May 8, 2012. Retrieved October 4, 2012.
  35. ^ "ISO/IEC 23270:2006 - Information technology - Programming languages - C#". Iso.org. January 26, 2012. Retrieved October 4, 2012.
  36. ^ "SO/IEC 23270:2018 Information technology — Programming languages — C#". ISO. Retrieved November 26, 2020.
  37. ^ Mariani, Rico (October 5, 2009). "My History of Visual Studio (Part 1) – Rico Mariani's Performance Tidbits". Rico Mariani's Performance Tidbits.
  38. ^ Kovacs, James (September 7, 2007). "C#/.NET History Lesson". Archived from the original on March 6, 2009. Retrieved June 18, 2009.
  39. ^ Hejlsberg, Anders (October 1, 2008). "The A-Z of Programming Languages: C#". Computerworld. Archived from the original on April 2, 2015. Retrieved June 22, 2014.
  40. ^ "Microsoft C# FAQ". Microsoft. Archived from the original on February 14, 2006. Retrieved March 25, 2008.
  41. ^ "F# FAQ". Microsoft Research. Archived from the original on February 18, 2009. Retrieved June 18, 2009.
  42. ^ Simon, Raphael; Stapf, Emmanuel; Meyer, Bertrand (June 2002). "Full Eiffel on the .NET Framework". Microsoft. Retrieved June 18, 2009.
  43. ^ "What's new in the C# 2.0 Language and Compiler". Microsoft. Archived from the original on December 18, 2010. Retrieved June 11, 2014.
  44. ^ Hejlsberg, Anders; Torgersen, Mads (April 30, 2007). "Overview of C# 3.0". Microsoft Developer Network. Microsoft. Retrieved June 11, 2014.
  45. ^ a b "Using C# 3.0 from .NET 2.0". Danielmoth.com. May 13, 2007. Retrieved October 4, 2012.
  46. ^ Hejlsberg, Anders (September 15, 2011). "Future directions for C# and Visual Basic". Channel 9. BUILD2011. Microsoft. Archived from the original on September 23, 2011. Retrieved September 21, 2011.
  47. ^ "An Introduction to New Features in C# 5.0". The Microsoft MVP Award Program Blog. Microsoft. March 26, 2012. Archived from the original on June 4, 2014. Retrieved June 11, 2014.
  48. ^ "Languages features in C# 6 and VB 14". GitHub. dotnet/roslyn. Archived from the original on January 12, 2016. Retrieved February 13, 2015.
  49. ^ "What's new in C# 7". Microsoft Docs. December 21, 2016. Archived from the original on November 1, 2017.
  50. ^ Torgersen, Mads (March 9, 2017). "New Features in C# 7.0". .NET Blog. Microsoft. Retrieved June 9, 2017.
  51. ^ "Visual Studio 2017 version 15.0 Release Notes". Microsoft Learn. April 11, 2023. Retrieved April 19, 2023.
  52. ^ "What's new in C# 7.1". Microsoft Docs. Retrieved October 9, 2017.
  53. ^ "Visual Studio 2017 version 15.3 Release Notes". Microsoft Learn. April 11, 2023. Archived from the original on March 21, 2023. Retrieved April 19, 2023.
  54. ^ "What's new in C# 7.2". Microsoft Docs. Retrieved November 26, 2017.
  55. ^ "Visual Studio 2017 version 15.5 Release Notes". Microsoft Learn. April 11, 2023. Archived from the original on April 20, 2023. Retrieved April 19, 2023.
  56. ^ "What's new in C# 7.3". Microsoft Docs. Retrieved June 23, 2018.
  57. ^ "Visual Studio 2017 version 15.7 Release Notes". Microsoft Learn. July 13, 2022. Retrieved April 19, 2023.
  58. ^ "What's new in C# 8.0". Microsoft Docs. March 9, 2023.
  59. ^ "Visual Studio 2019 version 16.3 Release Notes". Microsoft Learn. April 11, 2023. Archived from the original on April 20, 2023. Retrieved April 19, 2023.
  60. ^ BillWagner. "What's new in C# 9.0 - C# Guide". Microsoft Learn. Retrieved October 15, 2020.
  61. ^ "Visual Studio 2019 version 16.8 Release Notes". Microsoft Learn. April 11, 2023. Retrieved April 19, 2023.
  62. ^ "What's new in C# 10". Microsoft Learn. Retrieved November 10, 2021.
  63. ^ "Visual Studio 2022 version 17.0 Release Notes". Microsoft Learn. Retrieved April 19, 2023.
  64. ^ "What's new in C# 11". Microsoft Learn. Retrieved August 8, 2022.
  65. ^ "Visual Studio 2022 version 17.4 Release Notes". Microsoft Learn. Retrieved April 19, 2023.
  66. ^ "What's new in C# 12". Microsoft Learn. Retrieved June 29, 2023.
  67. ^ "Visual Studio 2022 version 17.6 Release Notes". Microsoft Learn. Retrieved June 29, 2023.
  68. ^ Novák et al. 2010.
  69. ^ stevewhims; mattwojo (October 20, 2022). "Compiling Apps with .NET Native - UWP applications". learn.microsoft.com. Retrieved October 27, 2023.
  70. ^ LakshanF; agocke; Rick-Anderson; et al. (September 12, 2023). "Native AOT deployment overview - .NET". learn.microsoft.com. Retrieved October 27, 2023.((cite web)): CS1 maint: numeric names: authors list (link)
  71. ^ BillWagner. "Expression Trees (C#)". Microsoft Learn. Retrieved May 14, 2021.
  72. ^ dotnet-bot. "System.Reflection.Emit Namespace". learn.microsoft.com. Retrieved April 28, 2023.
  73. ^ McAllister, Neil (October 20, 2011). "Microsoft's Roslyn: Reinventing the compiler as we know it". InfoWorld. Retrieved March 5, 2022.
  74. ^ "Introducing C# Source Generators". .NET Blog. April 29, 2020. Retrieved May 14, 2021.
  75. ^ "virtual (C# Reference)". Microsoft Learn. September 15, 2021.
  76. ^ "Auto-Implemented Properties (C# Programming Guide)". Retrieved September 12, 2020.
  77. ^ "using directive - C# Reference". Microsoft Docs. Retrieved April 14, 2019.
  78. ^ BillWagner. "Unsafe code, pointers to data, and function pointers". Microsoft Learn. Retrieved June 20, 2021.
  79. ^ "How to create user-defined exceptions". Retrieved September 12, 2020.
  80. ^ Venners, Bill; Eckel, Bruce (August 18, 2003). "The Trouble with Checked Exceptions". Retrieved March 30, 2010.
  81. ^ BillWagner. "Operator overloading - C# reference". Microsoft Learn. Retrieved June 20, 2021.
  82. ^ Zhang, Xue Dong; Teng, Zi Mu; Zhao, Dong Wang (September 2014). "Research of the Database Access Technology Under.NET Framework". Applied Mechanics and Materials. 644–650: 3077–3080. doi:10.4028/www.scientific.net/AMM.644-650.3077. S2CID 62201466. ProQuest 1565579768.
  83. ^ Otey, Michael (February 2006). "LINQ to the Future". SQL Server Magazine. Vol. 8, no. 2. pp. 17–21. ProQuest 214859896.
  84. ^ Sheldon, William (November 2010). "New Features in LINQ". SQL Server Magazine. Vol. 12, no. 11. pp. 37–40. ProQuest 770609095.
  85. ^ BillWagner (September 15, 2021). "Query Syntax and Method Syntax in LINQ (C#)". learn.microsoft.com. Retrieved May 23, 2023.
  86. ^ erikdietrich (March 9, 2023). "The history of C# - C# Guide". learn.microsoft.com. Retrieved April 28, 2023.
  87. ^ The functional journey of C# - Mads Torgersen - NDC Copenhagen 2022, retrieved May 15, 2023
  88. ^ "The Beauty of Closures". csharpindepth.com. Retrieved April 28, 2023.
  89. ^ a b BillWagner. "Anonymous functions - C# Programming Guide". Microsoft Learn. Retrieved May 15, 2021.
  90. ^ a b c "What's New in C# 7.0". Microsoft Docs. Retrieved April 14, 2019.
  91. ^ "C# 9.0 on the record". .NET Blog. November 10, 2020. Retrieved May 15, 2021.
  92. ^ BillWagner (June 30, 2022). "init keyword - C# Reference". learn.microsoft.com. Retrieved May 19, 2023.
  93. ^ The .NET Compiler Platform, .NET Platform, April 28, 2023, retrieved April 28, 2023
  94. ^ a b c d Archer 2001.
  95. ^ Lippert, Eric (March 19, 2009). "Representation and Identity". Fabulous Adventures In Coding. Blogs.msdn.com. Retrieved October 4, 2012.
  96. ^ "Framework Libraries". Microsoft Learn. April 19, 2023.
  97. ^ BillWagner. "What's new in C# 9.0 - C# Guide". Microsoft Learn. Retrieved May 14, 2021.
  98. ^ BillWagner. "Main() and command-line arguments". Microsoft Learn. Retrieved August 5, 2021.
  99. ^ "Patent Pledge for Open Source Developers". March 16, 2023.
  100. ^ "Patent Cooperation Agreement - Microsoft & Novell Interoperability Collaboration". Microsoft. November 2, 2006. Archived from the original on May 17, 2009. Retrieved July 5, 2009. Microsoft, on behalf of itself and its Subsidiaries (collectively "Microsoft"), hereby covenants not to sue Novell's Customers and Novell's Subsidiaries' Customers for infringement under Covered Patents of Microsoft on account of such a Customer's use of specific copies of a Covered Product as distributed by Novell or its Subsidiaries (collectively "Novell") for which Novell has received Revenue (directly or indirectly) for such specific copies; provided the foregoing covenant is limited to use by such Customer (i) of such specific copies that are authorized by Novell in consideration for such Revenue, and (ii) within the scope authorized by Novell in consideration for such Revenue.
  101. ^ "Definitions". Microsoft. November 2, 2006. Retrieved July 5, 2009.
  102. ^ Steinman, Justin (November 7, 2006). "Novell Answers Questions from the Community". Retrieved July 5, 2009. We maintain that Mono does not infringe any Microsoft patents.
  103. ^ "Covenant to Downstream Recipients of Moonlight - Microsoft & Novell Interoperability Collaboration". Microsoft. September 28, 2007. Archived from the original on September 23, 2010. Retrieved March 8, 2008. "Downstream Recipient" means an entity or individual that uses for its intended purpose a Moonlight Implementation obtained directly from Novell or through an Intermediate Recipient... Microsoft reserves the right to update (including discontinue) the foregoing covenant... "Moonlight Implementation" means only those specific portions of Moonlight 1.0 or Moonlight 1.1 that run only as a plug-in to a browser on a Personal Computer and are not licensed under GPLv3 or a Similar License.
  104. ^ a b "The RyuJIT transition is complete!". microsoft.com. June 19, 2018. Archived from the original on July 19, 2019. Retrieved July 20, 2021.
  105. ^ "Managed Execution Process". microsoft.com. Archived from the original on December 23, 2017. Retrieved July 20, 2021.
  106. ^ "coreclr/src/jit/". github.com. Archived from the original on January 9, 2019. Retrieved July 20, 2021.
  107. ^ "C# Guide". Microsoft Learn.
  108. ^ "5.0.8". microsoft.com. Archived from the original on April 23, 2020. Retrieved July 20, 2021.
  109. ^ "Mitigation: New 64-bit JIT Compiler". microsoft.com. Archived from the original on April 5, 2018. Retrieved July 20, 2021.
  110. ^ Etcheverry, Ignacio (October 21, 2017). "Introducing C# in Godot". Godot Engine. Archived from the original on October 26, 2018. Retrieved October 26, 2018.

Further reading