User Tools

Site Tools


c_sharp

C#

Return to Effective C Sharp by Cloud Monk, Effective dot NET, Anders Hejlsberg, Microsoft, C# .NET, TypeScript, C# Topics, C# Bibliography, Awesome C#

Snippet from Wikipedia: C Sharp (programming language)

C# ( see SHARP) is a general-purpose high-level programming language supporting multiple paradigms. C# encompasses static typing,: 4  strong typing, lexically scoped, imperative, declarative, functional, generic,: 22  object-oriented (class-based), and component-oriented programming disciplines.

The principal inventors of the C# programming language were Anders Hejlsberg, Scott Wiltamuth, and Peter Golde from Microsoft. It was first widely distributed in July 2000 and was later approved as an international standard by Ecma (ECMA-334) in 2002 and ISO/IEC (ISO/IEC 23270 and 20619) 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.

“C# is a general-purpose, type-safe, primarily object-oriented programming language, the goal of which is programmer productivity. To this end, the language balances simplicity, expressiveness, and performance. C# 9 is designed to work with the Microsoft .NET 5 runtime (whereas C# 8 targets .NET Core 3, and C# 7 targets .NET Core 2 and Microsoft .NET Framework 4.6/4.7/4.8).”

Fair Use Source: B08SYWWDTX


Most Useful Sites

C# .NET - C Sharp Dot NET

<!– Per Ecma, “C#” (i.e. not “C♯”) is the standard spelling of the name of the language. See “Language name” section and talk page. –>

<ref>

</ref>

</ref> D, J#, Dart,<ref>

</ref> F#, Hack, Java,<ref>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 ://www.barrycornelius.com/papers/java5/ ://www.levenez.com/lang/</ref><ref name=“influenced” /> Kotlin, Nemerle, Oxygene, Ring,<ref name=“Ring programming language and other languages”>

</ref> Rust, Swift,<ref name=“lattner2014”>

</ref> Vala, TypeScript

}}

}}

C# (pronounced see sharp, like the musical note C♯, but written with the number sign)

is a general-purpose, multi-paradigm programming language encompassing static typing, strong typing, lexically scoped, imperative, declarative<!–e.g. attributes–>, functional, generic, object-oriented (class-based), and component-oriented programming disciplines.<ref name=“ECMA-334” />

C# was developed around 2000 by Microsoft as part of its .NET initiative and later approved as an international standard by Ecma (ECMA-334) in 2002 and ISO (ISO/IEC 23270) in 2003. It was designed by Anders Hejlsberg, and its development team is currently led by Mads Torgersen, being one of the programming languages designed for the Common Language Infrastructure (CLI). The most recent version is 9.0, which was released in 2020 in .NET 5.0 and included in Visual Studio 2019 version 16.8.<ref>

</ref><ref>

</ref>

Mono is a free and open-source project to develop a cross-platform compiler and runtime environment (i.e. virtual machine) for the language.

Design goals

The Ecma standard lists these design goals for C#:<ref name=“ECMA-334”>

</ref>

  • The language is intended to be a simple, modern, general-purpose, object-oriented programming language.
  • The language, and implementations thereof, should provide support for software engineering principles such as strong type checking, array bounds checking, detection of attempts to use uninitialized variables, and automatic garbage collection. Software robustness, durability, and programmer productivity are important.
  • The language is intended for use in developing software components suitable for deployment in distributed environments.
  • Portability is very important for source code and programmers, especially those already familiar with C and C++.
  • Support for internationalization is very important.
  • C# is intended to be suitable for writing applications for both hosted and embedded systems, ranging from the very large that use sophisticated operating systems, down to the very small having dedicated functions.
  • Although C# applications are intended to be economical with regard to memory and processing power requirements, the language was not intended to compete directly on performance and size with C or assembly language.

History

During the development of the .NET Framework, the class libraries were originally written using a managed code compiler system called “Simple Managed C” (SMC).<ref>

</ref><ref>

</ref> 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”.<ref name=“computerworld2008”>

</ref> 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<ref>

</ref> 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.”<ref name=“gosling”>

</ref><ref>

</ref> Klaus Kreft and Angelika Langer (authors of a C++ streams book) stated in a blog post that “Java and C# are almost identical programming languages. Boring repetition that lacks innovation,”<ref name=“kreft-langer”>

</ref> “Hardly anybody will claim that Java or C# are revolutionary programming languages that changed the way we write programs,” and “C# borrowed a lot from Java - and vice versa. Now that C# supports boxing and unboxing, we'll have a very similar feature in Java.”<ref>

</ref> In July 2000, Hejlsberg said that C# is “not a Java clone” and is “much closer to C++” in its design.<ref name=“JohnOsborn”>

</ref>

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.<ref>

</ref> 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.<ref>

</ref> 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.<ref>

</ref>

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

</ref>

C# was originally submitted to the ISO subcommittee JTC 1/SC 22 for review,<ref>

</ref> under ISO/IEC 23270:2003,<ref>

</ref> was withdrawn and was then approved under ISO/IEC 23270:2006.<ref>

</ref> The 23270:2006 is withdrawned under 23270:2018 and approved with this version.<ref>

</ref>

Name

Microsoft first used the name C# in 1988 for a variant of the C language designed for incremental compilation.<ref>

</ref> That project was not completed but the name lives on.

File:Treblecsharp5.svg

]] 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.<ref>

</ref> 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++.<ref>

</ref>

Due to technical limitations of display (standard fonts, browsers, etc.) and the fact that the sharp symbol (

) is not present on most keyboard layouts, the number sign (

) was chosen to approximate the sharp symbol in the written name of the programming language.<ref name=“MS CSharp FAQ”>

</ref> This convention is reflected in the ECMA-334 C# Language Specification.<ref name=“ECMA-334”/>

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#.<ref name=“MS FSharp FAQ”>

</ref> The original implementation of Eiffel for .NET was called Eiffel#,<ref>

</ref> 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).

Versions

Version Language specification Date .NET Visual Studio
Ecma ISO/IEC Microsoft
C# 1.0 December 2002 April 2003 January 2002 January 2002 .NET Framework 1.0 Visual Studio .NET 2002
C# 1.1<br/>C# 1.2 October 2003 April 2003 .NET Framework 1.1 Visual Studio .NET 2003
C# 2.0<ref>

</ref>

June 2006 September 2006 September 2005

November 2005 .NET Framework 2.0<br/>.NET Framework 3.0 Visual Studio 2005<br/>Visual Studio 2008
C# 3.0<ref>

</ref>

colspan=“2” rowspan=“2”

August 2007 November 2007 .NET Framework 2.0 (Except LINQ)<ref name=“danielmoth1”>

</ref><br/> .NET Framework 3.0 (Except LINQ)<ref name=“danielmoth1”/><br/> .NET Framework 3.5

Visual Studio 2008
C# 4.0<ref>

</ref>

April 2010 April 2010 .NET Framework 4 Visual Studio 2010
C# 5.0<ref>

</ref>

December 2017 December 2018 June 2013 August 2012 .NET Framework 4.5 Visual Studio 2012<br/>Visual Studio 2013
C# 6.0<ref>

</ref>

colspan=“2” rowspan=“7”

Draft July 2015 .NET Framework 4.6<br/>.NET Core 1.0<br/>.NET Core 1.1 Visual Studio 2015
C# 7.0<ref>

</ref><ref name=“new_features_in_7”>

</ref>

Specification proposal March 2017 .NET Framework 4.7 Visual Studio 2017 version 15.0
C# 7.1<ref>

</ref>

Specification proposal August 2017 .NET Core 2.0 Visual Studio 2017 version 15.3<ref>

</ref>

C# 7.2<ref>

</ref>

Specification proposal November 2017 Visual Studio 2017 version 15.5<ref name=“visualstudio.com.2017”>

</ref>

C# 7.3<ref>

</ref>

Specification proposal May 2018 .NET Core 2.1<br/>.NET Core 2.2<br/>.NET Framework 4.8 Visual Studio 2017 version 15.7<ref name=“visualstudio.com.2017”/>
C# 8.0<ref>

</ref>

Specification proposal September 2019 .NET Core 3.0<br/>.NET Core 3.1 Visual Studio 2019 version 16.3<ref name=“visualstudio.com.2019”>

</ref>

C# 9.0<ref>

</ref>

Specification proposal September 2020 .NET 5.0 Visual Studio 2019 version 16.8<ref name=“visualstudio.com.2019”/>

Syntax

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

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

Portability

By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure&nbsp;(CLI).<ref>

</ref> 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. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or Fortran.

Typing

C# supports strongly typed implicit variable declarations with the keyword

var

, and implicitly typed arrays with the keyword

new[]

followed by a collection initializer.

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, 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++. <!–NOTE TO EDITORS: Classes do NOT *NEED* to go in a Namespace. Check the spec or try it out yourself before stating otherwise.–>

Metaprogramming

Metaprogramming via C# attributes is part of the language. Many of these attributes duplicate the functionality of GCC's and VisualC++'s platform-dependent preprocessor directives.

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.<ref>

</ref>

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.

The type

dynamic

allows for run-time method binding, allowing for JavaScript-like method calls and run-time object composition.

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

.

Property

C# supports class 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,<ref name=“auto-implemented property”>

</ref> where the accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class.

Namespace

A C#

namespace

provides the same level of code isolation as a Java

package

or a C++

, with very similar rules and features to a

package

. Namespaces can be imported with the “using” syntax.<ref>

</ref>

Memory access

In C#, memory address pointers can only be used within blocks specifically marked as unsafe, 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 garbage-collected objects, array, string, or a block of stack-allocated memory. 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.

Exception

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 specific handling to be put in place for particular circumstances as needed.<ref>

</ref>

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.<ref>

</ref>

Polymorphism

Unlike C++, C# does not support multiple inheritance, although a class can implement any number of interfaces. 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. Only the most commonly overloaded operators in C++ may be overloaded in C#.

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&lt;T&gt;

interface is implemented on the object. This includes XML documents, an ADO.NET dataset, and SQL databases.<ref>

|doi=10.4028/www.scientific.net/AMM.644-650.3077 |s2cid=62201466 }}</ref>

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.<ref>

}}</ref> 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.<ref>

}}</ref>

Functional programming

Though primarily an imperative language, C# 2.0 offered limited support for functional programming through first-class functions and closures in the form of anonymous delegates. C# 3.0 expanded support for functional programming with the introduction of a lightweight syntax for lambda expressions, extension methods (an affordance for modules), and a list comprehension syntax in the form of a “query comprehension” language. C# 7.0 adds features typically found in functional languages like tuples and pattern matching.<ref>

</ref>

Common type system

C# has a unified type system. This unified type system is called Common Type System (CTS).<ref name=“insidecsharpp2ch4”>

</ref>

A unified type system implies that all types, including primitives such as integers, are subclasses of the

class. For example, every type inherits a

method.

Categories of data types

CTS separates data types into two categories:<ref name=“insidecsharpp2ch4” />

  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

, 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. Examples of value types are all primitive types, such as

(a signed 32-bit integer),

(a 32-bit IEEE floating-point number),

(a 16-bit Unicode code unit), and

(identifies a specific point in time with nanosecond precision). Other examples are

(enumerations) and

(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

). 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

or

). Examples of reference types are

(the ultimate base class for all other C# classes),

(a string of Unicode characters), and

(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.<ref name=“insidecsharpp2ch4” /> 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.<ref name=“insidecsharpp2ch4” /> 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).<ref>

</ref>

Example: <syntaxhighlight lang=“CSharp”> int foo = 42; // Value type. object bar = foo; // foo is boxed to bar. int foo2 = (int)bar; // Unboxed back to value type. </syntaxhighlight>

Libraries

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.<ref>

</ref>

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

Examples

Hello World

The following is a very simple C# program, a version of the classic “Hello world” example:

<syntaxhighlight lang=“csharp”> using System;

// A version of the classic “Hello World” program class Program {

   public static void Main(string[] args)
   {
       Console.WriteLine("Hello, world!");
   }
} </syntaxhighlight>

This code will display this text in the console window:

Hello, world!

Each line has a purpose:

<syntaxhighlight lang=“CSharp”> using System; </syntaxhighlight>

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).

<syntaxhighlight lang=“csharp”> // A version of the classic “Hello World” program </syntaxhighlight>This line is a comment; it describes and documents the code for the programmer(s).<syntaxhighlight lang=“CSharp”> class Program </syntaxhighlight>

Above is a class definition for the

class. Everything that follows between the pair of braces describes that class.<syntaxhighlight lang=“csharp”> {

   ...
} </syntaxhighlight>The curly brackets demarcate the boundaries of a code block. In this first instance, they are marking the start and end of the

class.<syntaxhighlight lang=“csharp”> public static void Main(string[] args) </syntaxhighlight>

This declares the class member method where the program begins execution. The .NET runtime calls the

method. (Note:

may also be called from elsewhere, like any other method, e.g. from another method of

.) The

keyword tells the compiler that the method can be called from anywhere by any class. The static keyword makes the method accessible without an instance of

. Each console application's

entry point must be declared

otherwise the program would require an instance of

, 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

method. The

keyword declares that

has no return value.

<syntaxhighlight lang=“CSharp”> Console.WriteLine(“Hello, world!”); </syntaxhighlight>

This line writes the output.

is a static class in the

namespace. It provides an interface to the standard input, output, and error streams for console applications. The program calls the

method

, which displays on the console a line with the argument, the string

.

GUI

A GUI example:

<syntaxhighlight lang=“CSharp”> using System; using System.Windows.Forms;

class Program {

   static void Main()
   {
       MessageBox.Show("Hello, World!");
       Console.WriteLine("Is almost the same argument!");
   }
} </syntaxhighlight>

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.

Images

Another useful library is the

System.Drawing

library, which is used to programmatically draw images. For example:<syntaxhighlight lang=“c#”> using System; using System.Drawing;

public class Example {

   public static Image img;
   public static void Main()
   {
       img = Image.FromFile("Image.png");
   }
} </syntaxhighlight>This will create an image that is identical to that stored in “Image.png”.

Standardization and licensing

In August 2001, Microsoft Corporation, Hewlett-Packard and Intel Corporation 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 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, 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 and Ecma standards that provide reasonable and non-discriminatory licensing protection from patent claims.

Microsoft has 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 OSP.<ref>

</ref> Microsoft has also agreed not to enforce patents relating to Novell products against Novell's paying customers<ref>

</ref> with the exception of a list of products that do not explicitly mention C#, .NET or Novell's implementation of .NET (The Mono Project).<ref>

</ref> However, Novell maintains that Mono does not infringe any Microsoft patents.<ref>

</ref> Microsoft has 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.<ref name=“MsCovenant”>

</ref>

Implementations

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), the second one RyuJIT,<ref>https://devblogs.microsoft.com/dotnet/the-ryujit-transition-is-complete/</ref> 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.<ref>https://docs.microsoft.com/en-us/dotnet/standard/managed-execution-process</ref> RuyJIT is open source and written in C++.<ref>https://github.com/dotnet/coreclr/tree/master/src/jit</ref> 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.<ref name=“auto”/><ref>

</ref> Two branches of official implementation are the .NET (closed sources, Windows 10 only since .NET 4.6.2) and the .NET core (open source, multiplatform); .NET and .NET core are converging into one open source implementation .NET 5.0.<ref>https://dotnet.microsoft.com/download/dotnet/5.0</ref> At .NET 4.6 a new JIT compiler replaced the former.<ref>https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/mitigation-new-64-bit-jit-compiler</ref><ref>https://devblogs.microsoft.com/dotnet/the-ryujit-transition-is-complete/</ref>

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

  • The Mono project provides an open-source C# compiler, a complete open-source implementation of the Common Language Infrastructure including the required framework libraries as they appear in the ECMA specification, and a nearly complete implementation of the Microsoft proprietary .NET class libraries up to .NET 3.5. As of Mono 2.6, no plans exist to implement WPF; WF is planned for a later release; and there are only partial implementations of LINQ to SQL and WCF.<ref>

    </ref>

  • The Elements tool chain from RemObjects includes RemObjects C#, which compiles C# for .NET, Java, Cocoa, Android, Windows, Linux and WebAssembly.* The DotGNU project (now discontinued) also provided an open-source C# compiler, a nearly complete implementation of the Common Language Infrastructure including the required framework libraries as they appear in the ECMA specification, and subset of some of the remaining Microsoft proprietary .NET class libraries up to .NET 2.0 (those not documented or included in the ECMA specification, but included in Microsoft's standard .NET Framework distribution).
  • Xamarin provides tools to develop cross-platform applications for common mobile and desktop operating systems, using C# as a codebase and compiling to native code.

Mono is a common choice for game engines due to its cross-platform nature

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

</ref>

See also

Notes

References

</ref>

<ref name=“influenced by CPP”>

</ref>

<ref name=“influenced by op”>

</ref>

<ref name=“influenced”>

</ref> }}

Further reading

American inventions Programming languages C Sharp programming language family .NET programming languages Class-based programming languages Ecma standards Functional languages IEC standards ISO standards Multi-paradigm programming languages Programming languages created in 2000 Programming languages with an ISO standard Statically typed programming languages 2000 software

Snippet from Wikipedia: C Sharp (programming language)

C# ( see SHARP) is a general-purpose high-level programming language supporting multiple paradigms. C# encompasses static typing,: 4  strong typing, lexically scoped, imperative, declarative, functional, generic,: 22  object-oriented (class-based), and component-oriented programming disciplines.

The principal inventors of the C# programming language were Anders Hejlsberg, Scott Wiltamuth, and Peter Golde from Microsoft. It was first widely distributed in July 2000 and was later approved as an international standard by Ecma (ECMA-334) in 2002 and ISO/IEC (ISO/IEC 23270 and 20619) 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.

Snippet from Wikipedia: .NET Framework

The .NET Framework (pronounced as "dot net") is a proprietary software framework developed by Microsoft that runs primarily on Microsoft Windows. It was the predominant implementation of the Common Language Infrastructure (CLI) until being superseded by the cross-platform .NET project. It includes a large class library called Framework Class Library (FCL) and provides language interoperability (each language can use code written in other languages) across several programming languages. Programs written for .NET Framework execute in a software environment (in contrast to a hardware environment) named the Common Language Runtime (CLR). The CLR is an application virtual machine that provides services such as security, memory management, and exception handling. As such, computer code written using .NET Framework is called "managed code". FCL and CLR together constitute the .NET Framework.

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

.NET Framework began as proprietary software, although the firm worked to standardize the software stack almost immediately, even before its first release. Despite the standardization efforts, developers, mainly those in the free and open-source software communities, expressed their unease with the selected terms and the prospects of any free and open-source implementation, especially regarding software patents. Since then, Microsoft has changed .NET development to more closely follow a contemporary model of a community-developed software project, including issuing an update to its patent promising to address the concerns.

In April 2019, Microsoft released .NET Framework 4.8, the last major version of the framework as a proprietary offering, followed by .NET Framework 4.8.1 in August 2022. Only monthly security and reliability bug fixes to that version have been released since then. No further changes to that version are planned. The .NET Framework will continue to be included with future releases of Windows and continue to receive security updates, with no plans to remove it as of September 2024.


https://softwareengineering.stackexchange.com/tags/c%23/info

C# is a multiparadigm, managed, garbage-collected object-oriented programming language created by Microsoft in conjunction with the .NET platform, but also used with non-Microsoft implementations (most notably, Mono).

Versions 1.0/1.2 and 2.0 of C# were submitted and approved as both ECMA and ISO/IEC standards. As of December 2010, there are no ECMA or ISO/IEC specifications for C# 3.0 and 4.0, however language specifications are available from Microsoft (3.0 and 4.0 respectively).

The language's type-system was originally static, with only explicit variable declarations allowed. However, the introduction of var (C# 3.0) and dynamic (C# 4.0) allow it to use type-inference for implicit variable typing, and to consume dynamic type-systems, respectively. Delegates (especially with lexical-closure support for anonymous-methods (C# 2.0) and lambda-expressions (C# 3.0)) allow the language to be used for functional programming.

Compilation is usually to the Common Intermediate Language (CIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR); however, options like Ngen (.NET) and AOT (Mono) mean this isn't the only option. Additionally, some frameworks (e.g. the Micro Framework) act as CIL interpreters, with no JIT.

Perhaps unusually, generics in C# are provided (in part) by the runtime, unlike (for comparison) C++ templates, or Java's generics (which use type-erasure).

With the combination of Microsoft .NET for Windows (desktop/server), Mono (desktop/server/mobile), Silverlight / Moonlight (browser/mobile), Compact Framework (mobile), and Micro Framework (embedded devices), it is available for a wide range of platforms.

Hello World

using System; class Hello {

   static void Main() 
   {
       Console.WriteLine("Hello, World");
   }
}

FAQs

   What are the correct version numbers for C#?
   Why is Random giving the same results every time?
   Captured variables in loops
   Why can't I convert List to List?
   Does C# pass objects by reference?

Resources

   Specification
   Wikipedia Article
   Eric Lippert's blog
   Programming Guide
   Books
       CLR via C#
       C# in a Nutshell
       C# in Depth
       Accelerated C#
       Head First C#
       The C# Programming Language (3rd Edition, 4th Edition)
       Framework Design Guidelines
       Essential C# (4.0 (3rd Edition))

https://rosettacode.org/wiki/Category:C_sharp

c_sharp.txt · Last modified: 2024/08/26 12:53 by 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki