Mono (software)

Mono is a free and open-source project to create an Ecma standard-compliant .NET Framework-compatible software framework, including a C# compiler and a Common Language Runtime. Originally by Ximian, it was later acquired by Novell, and is now being led by Xamarin, a subsidiary of Microsoft[3] and the .NET Foundation. The stated purpose of Mono is not only to be able to run Microsoft .NET applications cross-platform, but also to bring better development tools to Linux developers.[4] Mono can be run on many software systems including Android, most Linux distributions, BSD, macOS, Windows, Solaris, and even some game consoles such as PlayStation 3, Wii, and Xbox 360.

Mono
Diagram of Mono architecture
Original author(s)Ximian
Developer(s).NET Foundation and Xamarin (a Microsoft subsidiary)
Initial releaseJune 30, 2004 (2004-06-30)
Stable release
6.10.0.105 / May 15, 2020 (2020-05-15)[1]
Preview release
6.12.0.86 / June 30, 2020 (2020-06-30)[1]
Repository
Written inC, C#, XML
Operating systemWindows, macOS, Linux
PlatformIA-32, x64, IA-64, ARM, MIPS, PowerPC, SPARC, S390
TypeSoftware framework
LicenseMIT License[2]
Websitemono-project.com

The Mono project has been controversial within the open-source community, as it implements portions of .NET Framework that may be covered by Microsoft patents. Although standardized portions of .NET Framework are covered under Microsoft Open Specification Promise—a covenant stating that Microsoft will not assert its patents against implementations of its specifications under certain conditions—other portions are not, which led to concerns that the Mono project could become the target of patent infringement lawsuits. Following Microsoft's open-sourcing of several core .NET technologies since 2014 and its acquisition of Xamarin in the beginning of 2016, an updated patent promise has been issued for the Mono project (§ Mono and Microsoft's patents).

The logo of Mono is a stylized monkey's face, mono being Spanish for monkey.[5]

History
Release History[6]
DateVersion[7]Notes
2004-06-301.0[8]C# 1.0 support
2004-09-211.1[9]
2006-11-091.2[10]C# 2.0 support
2008-10-062.0[11]Mono's APIs are now in par with .NET 2.0. Introduces the C# 3.0 and Visual Basic 8 compilers. New Mono-specific APIs: Mono.Cecil, Mono.Cairo and Mono.Posix. Gtk# 2.12 is released. The Gendarme verification tool and Mono Linker are introduced.
2009-01-132.2[12]Mono switches its JIT engine to a new internal representation[13] that gives it a performance boost and introduces SIMD support in the Mono.Simd[14] Mono.Simd namespace.
Mono introduces Full Ahead of Time compilation that allows developers to create full static applications and debuts the C# Compiler as a Service[15] and the C# Interactive Shell[16] (C# REPL)
2009-03-302.4[17]This release mostly polishes all the features that shipped in 2.2 and became the foundation for the Long-Term support of Mono in SUSE Linux.
2009-12-152.6[18]The Mono runtime is now able to use LLVM as a code generation backend and this release introduces Mono co-routines, the Mono Soft Debugger and the CoreCLR security system required for Moonlight and other Web-based plugins.
On the class library System.IO.Packaging, WCF client, WCF server, LINQ to SQL debut. The Interactive shell supports auto-completion and the LINQ to SQL supports multiple database backends. The xbuild build system is introduced.
2010-09-222.8[19]Defaults to .NET 4.0 profile, C# 4.0 support, new generational garbage collector, includes Parallel Extensions, WCF Routing, CodeContracts, ASP.NET 4.0, drops the 1.0 profile support; the LLVM engine tuned to support 99.9% of all generated code, runtime selectable llvm and gc; incorporates Dynamic Language Runtime, MEF, ASP.NET MVC2, OData Client open-source code from Microsoft;. Will become release 3.0
2011-02-152.10[20]
2012-10-183.0[21]C# 5.0 support, async support, Async Base Class Library Upgrade and MVC4 - Partial, no async features support.
2013-07-243.2[22]Default Garbage Collector is now the SGEN, instead of Boehm
2014-03-313.4[23]
2014-08-123.6[24]
2014-09-043.8[25]
2014-10-043.10[26]
2015-01-133.12[27]
2015-04-294.0[28]Defaults to .NET 4.5 profile and ships only .NET 4.5 assemblies, defaults to C# 6.0. First release to integrate Microsoft open-source .NET Core code
2017-05-105.0[29]Shipping Roslyn C# compiler to enable C#7 support; Shipping msbuild and deprecating xbuild for better compatibility; Enabling concurrent SGen garbage collector to reduce time spent in GC; Introducing the AppleTLS stack on macOS for HTTPS connections; Continued Progress on .NET Class Library convergence; Updated libjpeg in macOS package
2017-07-145.2[30]Support for .NET Standard 2.0, strong assembly names, and experimental default interface members.
2017-10-055.4[31]The JIT Runtime now supports concurrent method compilation and various other Performance Optimisations;
2018-02-015.8[32]Initial WebAssembly port; Modes for the SGen GC; Includes Roslyn's csi (C# interactive) REPL tool
2018-02-265.10[33]The Interpreter is now included in the default installation; runtime now supports Default Interface Methods; WebAssembly considered reliable now; Support for .NET 4.7.1 / C# 7.2 / F# 4.1
2018-05-085.12[34]Port to IBM AIX/i; now includes VB.NET compiler; option to use jemalloc
2018-08-075.14[35]Major Windows.Forms update to improve compatibility with .NET
2018-10-085.16[36]Hybrid suspend garbage collector; Client certificate support; C# 7.3 support
2018-12-215.18[37].NET 4.7.2 support; more CoreFX code is used
2019-07-17 6.0.0 C# compiler defaults to version C# 8.0 RC; Various stability improvement in debugger support; Mono Interpreter is feature complete and stable

When Microsoft first announced their .NET Framework in June 2000 it was described as "a new platform based on Internet standards",[38] and in December of that year the underlying Common Language Infrastructure was published as an open standard, "ECMA-335",[39] opening up the potential for independent implementations.[40] Miguel de Icaza of Ximian believed that .NET had the potential to increase programmer productivity and began investigating whether a Linux version was feasible.[41] Recognizing that their small team could not expect to build and support a full product, they launched the Mono open-source project, on July 19, 2001 at the O'Reilly conference.

After three years' development, Mono 1.0 was released on June 30, 2004.[42] Mono evolved from its initial focus of a developer platform for Linux desktop applications to supporting a wide range of architectures and operating systems - including embedded systems.[43]

Novell acquired Ximian in 2003. After Novell was acquired by Attachmate in April 2011, Attachmate announced hundreds of layoffs for the Novell workforce,[44] putting in question the future of Mono.[45][46]

On May 16, Miguel de Icaza announced in his blog that Mono would continue to be supported by Xamarin, a company he founded after being laid off from Novell. The original Mono team had also moved to the new company. Xamarin planned to keep working on Mono and had planned to rewrite the proprietary .NET stacks for iOS and Android from scratch, because Novell still owned MonoTouch and Mono for Android at the time.[47] After this announcement, the future of the project was questioned, MonoTouch and Mono for Android being in direct competition with the existing commercial offerings now owned by Attachmate, and considering that the Xamarin team would have difficulties proving that they did not use technologies they formerly developed when they were employed by Novell for the same work.[48] However, in July 2011, Novell, now a subsidiary of Attachmate, and Xamarin, announced that it granted a perpetual license to Xamarin for Mono, MonoTouch and Mono for Android, which officially took stewardship of the project.[49][50]

Current status and roadmap

Mono's current version is 6.0.0 (as of August 2019). This version provides the core API of the .NET Framework and support for Visual Basic.NET and C# 7.0. LINQ to Objects, XML, and SQL are part of the distribution. Windows Forms 2.0 is also supported, but not actively developed, and as such its support on Mono is incomplete.[51] Version 4.0 was the first version that incorporates Microsoft original source code that was released by Microsoft as part of the .NET Core project.

Mono's aim is to achieve full support for the features in .NET 4.5 except Windows Presentation Foundation (WPF) (which the Mono team do not plan to support due to the amount of work it would need),[51] Windows Workflow Foundation (WF), limited Windows Communication Foundation (WCF).[52] Some missing parts of the .NET Framework are under development in an experimental Mono subproject called Olive.[53]

The Mono project has also created a Visual Basic .NET compiler and a runtime designed for running VB.NET applications. It is currently being developed by Rolf Bjarne Kvinge.

Moonlight
Main article: Moonlight (runtime)

An open-source implementation of Microsoft Silverlight, called Moonlight, has been included since Mono 1.9.[54] Moonlight 1.0, which supports the Silverlight 1.0 APIs, was released January 20, 2009. Moonlight 2.0 supports Silverlight 2.0 and some features of Silverlight 3.0.[55] A preview release of Moonlight 3.0 was announced in February 2010 and contains updates to Silverlight 3 support.[56]

The Moonlight project was abandoned on May 29, 2012.[57] According to Miguel, two factors sealed the fate of the project: Microsoft added "artificial restrictions" that "made it useless for desktop programming", and the technology had not gained enough traction on the Web. In addition, Silverlight itself was deprecated by Microsoft by 2012.

Mono components

Mono consists of three groups of components:

  1. Core components
  2. Mono/Linux/GNOME development stack
  3. Microsoft compatibility stack

The core components include the C# compiler, the virtual machine for the Common Language Infrastructure and the core class libraries. These components are based on the Ecma-334 and Ecma-335 standards,[58] allowing Mono to provide a standards compliant, free and open-source CLI virtual machine. Microsoft issued a statement that covers both standards under their Community Promise license.[59]

The Mono/Linux/GNOME development stack provide tools for application development while using the existing GNOME and free and open-source libraries. These include: Gtk# for graphical user interface (GUI) development, Mozilla libraries for working with the Gecko rendering engine, Unix integration libraries (Mono.Posix), database connectivity libraries, a security stack, and the XML schema language RelaxNG. Gtk# allows Mono applications to integrate into the Gnome desktop as native applications. The database libraries provide connectivity to the object-relational database db4o, Firebird, Microsoft SQL Server (MSSQL), MySQL, Open Database Connectivity (ODBC), Oracle, PostgreSQL, SQLite, and many others. The Mono project tracks developing database components at its website.[60]

The Microsoft compatibility stack provides a pathway for porting Windows .NET applications to GNU/Linux. This group of components include ADO.NET, ASP.NET, and Windows Forms, among others. As these components are not covered by Ecma standards, some of them remain subject to patent fears and concerns.

Framework architecture

The major components of Mono include:

Code Execution Engine

The Mono runtime contains a code execution engine that translates ECMA CIL byte codes into native code and supports a number of processors: ARM, MIPS (in 32-bit mode only), SPARC, PowerPC, S390 (in 64-bit mode), x86, x86-64 and IA-64 for 64-bit modes.

The code generator is exposed in three modes:

  • Just-in-time (JIT) compilation: The runtime will turn ECMA CIL byte codes into native code as the code runs.
  • Ahead-of-Time (AOT) compilation: this code turns the ECMA CIL byte codes (typically found on a .exe or .dll file) and generates native code stored in an operating system, architecture and CPU specific file (for a foo.exe file, it would produce foo.exe.so on Linux). This mode of operation compiles most of the code that is typically done at runtime. There are some exceptions like trampolines and other administrative code that still require the JIT to function, so AOT images are not fully standalone.
  • Full Static Compilation: this mode is only supported on a handful of platforms and takes the Ahead-of-Time compilation process one step further and generates all the trampolines, wrappers and proxies that are required into a static file that can be statically linked into a program and completely eliminates the need for a JIT at runtime. This is used on Apple's iOS, Sony's PlayStation 3 and Microsoft's Xbox 360 operating systems.

Starting with Mono 2.6, it is possible to configure Mono to use the LLVM as the code generation engine instead of Mono's own code generation engine. This is useful for high performance computing loads and other situations where the execution performance is more important than the startup performance.

Starting with the Mono 2.7 preview, it is no longer necessary to pick one engine over the other at configuration time. The code generation engine can be selected at startup by using the --llvm or --nollvm command line arguments, and it defaults to the fast-starting Mono code generation engine.

Starting with Mono 5.18, support for LLVM is a defult configuration option. Previous versions required a special LLVM fork, but now mono can fall back to its own code generator when it encounters something not handled by LLVM.[61]

Garbage collector

As of Mono 2.8, the Mono runtime ships with two garbage collectors: a generational collector[62] and the Boehm conservative collector.

The default garbage collector prior to Mono 3.1.1 (the Boehm-Demers-Weiser Conservative Garbage Collector),[62][63] has significant limitations compared to commercial garbage-collected runtimes like the Java Virtual Machine or the .NET framework's runtime. Because the garbage collector could exhibit memory leaks on certain classes of applications, it may not have been suitable for long-running server applications prior to updating to 3.1.1 or later.

As of October 2010, a new generational collector called the Simple Generational GC (SGen-GC) became available as part of Mono. Starting with Mono 3.1.1 this is the default. For versions of Mono from 2.8 to 3.1.0, users can elect to use the SGen garbage collector by passing the --gc=sgen switch to the Mono runtime at startup.[62] This new garbage collector has many advantages over a traditional conservative scanner. It uses generational garbage collection where new objects are allocated from a nursery, during the garbage collection cycle, all objects that survived are migrated to an older generation memory pool. The idea being that many objects are transient and can quickly be collected and only a handful of objects are long-term objects that live for the entire life of the application. To improve performance this collector assigns memory pools to each thread to let threads allocate new memory blocks without having to coordinate with other threads. Migration of objects from the nursery to the old generation is done by copying the data from the nursery to the old generation pool and updating any live pointers that point to the data to point to the new location. This can be expensive for large objects, so Mono's SGen uses a separate pool of memory for large objects (Large Object Section) and uses a mark-and-sweep algorithm for those objects.

Currently SGen treats the stack and registers conservatively and pins any objects that could be referenced by any of these roots. The upcoming version of Mono scans the managed stack precisely, reducing the number of pinned objects.

Class library

The class library provides a comprehensive set of facilities for application development. They are primarily written in C#, but due to the Common Language Specification they can be used by any .NET language. The class library is structured into namespaces, and deployed in shared libraries known as assemblies. Speaking of the .NET framework is primarily referring to this class library.[64]

Namespaces and assemblies

Namespaces are a mechanism for logically grouping similar classes into a hierarchical structure. This prevents naming conflicts. The structure is implemented using dot-separated words, where the most common top-level namespace is System, such as System.IO and System.Net. There are other top-level namespaces as well, such as Accessibility and Windows. A user can define a namespace by placing elements inside a namespace block.

Assemblies are the physical packaging of the class libraries. These are .dll files, just like (but not to be confused with) Win32 shared libraries. Examples of assemblies are mscorlib.dll, System.dll, System.Data.dll and Accessibility.dll. Namespaces are often distributed among several assemblies and one assembly can be composed of several files.

Common Language Infrastructure and Common Language Specification

The Common Language Infrastructure (CLI) as implemented by the Common Language Runtime (CLR), is implemented by the Mono executable. The runtime compiles and executes .NET applications. The common language infrastructure is defined by the ECMA standard.[58] To run an application, you must invoke the runtime with the relevant parameters.

The Common Language Specification (CLS) is specified in chapter 6 of ECMA-335 and defines the interface to the CLI, such as conventions like the underlying types for Enum. The Mono compiler generates an image that conforms to the CLS. This is the Common Intermediate Language. The Mono runtime takes this image and runs it. The ECMA standard formally defines a library that conforms to the CLS as a framework.

Managed and unmanaged code

Within a native .NET/Mono application, all code is managed; that is, it is governed by the CLI's style of memory management and thread safety. Other .NET or Mono applications can use legacy code, which is referred to as unmanaged, by using the System.Runtime.InteropServices libraries to create C# bindings. Many libraries which ship with Mono use this feature of the CLI, such as Gtk#.

Mono-specific innovations

Mono has innovated in some areas with new extensions to the core C# and CLI specifications:

  • C# Compiler as a Service (Use the C# compiler as a library).[15]
  • C# Interactive Shell.[16]
  • SIMD support[14] as part of the Mono.SIMD namespace, where method calls to special vector types are directly mapped to the underlying processor CPU SIMD instructions.
  • Full static compilation of .NET code[65] (used on Mono/iPhone, Mono/PS3).
  • Mono coroutines (used to implement micro-threading code and continuations, mostly for game developers).[66]
  • Assembly injection to live processes.[67]
  • Use of LLVM as JIT backend.
  • Cxxi and CppSharp direct interop with C++ code and libraries.

In addition, Mono is available on a variety of operating systems and architectures.[68]

System requirements

Windows 7, Windows 8, Windows 8.1, Windows 10, macOS or Linux

Several projects extend Mono and allow developers to use it in their development environment. These projects include:

Cross-platform:

  • Banshee Media Player (stalled), a cross-platform music media player built with Mono and Gtk# and also a driver of dozens of C#-based libraries and projects for media handling.
  • Beagle (unmaintained), a search system for Unix systems.
  • Gecko#, bindings for embedding the layout engine used in Mozilla (Gecko).
  • Gtk#, C# wrappers around the underlying GTK+ and GNOME libraries, written in C and available on Linux, MacOS and Windows.
  • Mono Migration Analyzer (MoMA), a tool which aids Windows .NET developers in finding areas in their code that might not be cross-platform and therefore not work in Mono on Linux and other Unixes. Not upgraded since Mono 2.8 (2013); use Microsoft's .NET Portability Analyzer (dotnet-apiport) instead.
  • MonoCross, a cross-platform model–view–controller design pattern where the Model and Controller are shared across platforms and the Views are unique for each platform for an optimized User Interface. The framework requires Xamarin.iOS and Xamarin.Android.
  • MvvmCross, a cross-platform Model View ViewModel framework utilizing Xamarin.iOS and Xamarin.Android for developing mobile apps.
  • MonoDevelop an open-source and cross-platform integrated development environment that supports building applications for ASP.NET, Gtk#, Meego, MonoTouch and Silverlight/Moonlight.
  • Moonlight (discontinued), an implementation of Silverlight that uses Mono.
  • OpenTK, a managed binding for OpenGL, OpenCL and OpenAL.
  • QtSharp, C# bindings for the Qt framework.
  • Resco MobileBusiness, a cross-platform developer solution for mobile clients.
  • Resco MobileCRM, a cross-platform developer solution for mobile clients synchronized with Microsoft Dynamics CRM.
  • ServiceStack a high-performance open-source .NET REST web services framework that simplifies the development of XML, JSON and SOAP web services.
  • SparkleShare an open-source client software that provides cloud storage and file synchronization services.
  • Tao (superseded by OpenTK), a collection of graphics and gaming bindings (OpenGL, SDL, GLUT, Cg).
  • Xwt, a GUI toolkit that maps API calls to native platform calls of the underlying platform, exposing one unified API across different platforms and making possible for the graphical user interfaces to have native look and feel on different platforms. It enables building GUI-based desktop applications that run on multiple platforms, without having to customizing code for different platforms. Xwt API is mapped to a set of native controls on each supported platform. Features that are not available on specific platforms are emulated by using native widgets, which is referred to as hosting in the Xwt context.[69] Xwt was partially used as GUI toolkit (beside GTK#) in the development of the Xamarin Studio.[70] Supported "backend" engines are: WPF engine and Gtk engine (using Gtk#) on Windows, Cocoa engine (using MonoMac) and Gtk engine (using Gtk#) on Mac OS X, and Gtk engine (using Gtk#) on Linux.[71]

macOS:

  • Cocoa# – wrappers around the native macOS toolkit (Cocoa) (deprecated).
  • Monobjc – a set of bindings for macOS programming.
  • MonoMac – newer bindings for macOS programming, based on the MonoTouch API design.

Mobile platforms:

  • MonoDroid. Mono for the Android operating system. With bindings for the Android APIs.
  • MonoTouch. Mono for the iPhone, iPad and iPod Touches. With bindings to the iOS APIs.

Windows:

  • MonoTools for Visual Studio A Visual Studio plugin that allows Windows developers to target Linux and macOS right from Visual Studio and integrates with SUSE Studio.

Other implementations

Microsoft has a version of .NET 2.0 now available only for Windows XP, called the Shared Source CLI (Rotor). Microsoft's shared source license may be insufficient for the needs of the community (it explicitly forbids commercial use).

Free Software Foundation's decommissioned Portable.NET project.[72]

MonoDevelop
Main article: MonoDevelop

MonoDevelop is a free GNOME integrated development environment primarily designed for C# and other .NET languages such as Nemerle, Boo, and Java (via IKVM.NET), although it also supports languages such as C, C++, Python, and Vala. MonoDevelop was originally a port of SharpDevelop to Gtk#, but it has since evolved to meet the needs of Mono developers. The IDE includes class management, built-in help, code completion, Stetic (a GUI designer), project support, and an integrated debugger.

The MonoDoc browser provides access to API documentation and code samples. The documentation browser uses wiki-style content management, allowing developers to edit and improve the documentation.

Xamarin.iOS and Xamarin.Android

Xamarin.iOS and Xamarin.Android, both developed by Xamarin, are implementations of Mono for iPhone and Android-based smartphones. Previously available only for commercial licensing,[73] after Microsoft's acquisition of Xamarin in 2016, the Mono runtime itself was relicensed under MIT license[74] and both Xamarin.iOS and Xamarin.Android are being made free and open-source.[75]

Xamarin.iOS
Release History
DateVersionNotes
2009-09-14MonoTouch 1.0[76]Initial release
2010-04-05MonoTouch 2.0[77]iPad support
2010-04-16MonoTouch 3.0[78]iPhone 4 support
2011-04-06MonoTouch 4.0[79]iOS 4 support
2011-10-12MonoTouch 5.0[80]iOS 5 support
2012-09-19MonoTouch 6.0[81]iOS 6 support
2013-02-20Xamarin.iOS 6.2[82]Visual Studio support
2013-07-24Xamarin.iOS 6.4[83].NET 4.5 async/await support

Xamarin.iOS (previously named MonoTouch) is a proprietary library that allows developers to create C# and .NET based applications that run on the iPhone, iPod and iPad devices. It is based on the Mono framework and developed in conjunction with Novell. Unlike Mono applications, Xamarin.iOS "Apps" are compiled down to machine code targeted specifically at the Apple iPhone and iPad.[84] This is necessary because the iOS kernel prevents just-in-time compilers from executing on the device.

The Xamarin.iOS stack is made up of:

  • Compilers
    • C# from the Mono Project
    • Third-party compilers like RemObject's Oxygene can target Xamarin.iOS also
  • Core .NET libraries
  • Development SDK:
    • Linker – used to bundle only the code used in the final application
    • mtouch – the Native compiler and tool used to deploy to the target device
    • Interface Builder integration tools
  • Libraries that bind the native CocoaTouch APIs
  • Xamarin Studio IDE

Xamarin Studio is used as the primary IDE, however additional links to Xcode and the iOS simulator have been written.

From April to early September 2010, the future of MonoTouch was put in doubt as Apple introduced new terms for iPhone developers that apparently prohibits them from developing in languages other than C, C++ and Objective-C, and the use of a middle layer between the iOS platform and iPhone applications. This made the future of MonoTouch, and other technologies such as Unity, uncertain.[85] Then, in September 2010, Apple rescinded this restriction, stating that they were relaxing the language restrictions that they had put in place earlier that year.[86][87]

Xamarin.Android

Xamarin.Android (formerly known as Mono for Android), initially developed by Novell and continued by Xamarin, is a proprietary[88] implementation of Mono for Android-based smart-phones.[89][90][91] It was first released on April 6, 2011.[92] Mono for Android was developed to allow developers to more easily write cross-platform applications that will run on all mobile platforms.[93] In an interview with H-Online, Miguel de Icaza stated, "Our vision is to allow developers to reuse their engine and business logic code across all mobile platforms and swapping out the user interface code for a platform-specific API."[94]

In August 2010, a Microsoft spokesman, Tom Hanrahan of Microsoft's Open Source Technology Centre, stated, in reference to the lawsuit filed by Oracle against Google over Android's use of Java, that "The type of action Oracle is taking against Google over Java is not going to happen. If a .NET port to Android was through Mono it would fall under the Microsoft Community Promise Agreement."[95][96]

The Xamarin.Android stack consists of the following components:

  • Mono runtime
  • An Android UI designer[97]
  • Libraries:
    • Core .NET class libraries
    • Libraries that bind the native Android/Java APIs
  • SDK tools to package, deploy and debug
  • Xamarin Studio and Visual Studio 2010 integration to design the UI, remotely debug, and deploy.

License

Mono is dual licensed by Xamarin, similar to other products such as Qt and the Mozilla Application Suite. Mono's C# compiler and tools are released under the GNU General Public License (GPLv2 only) (starting with version 2.0 of Mono, the Mono C# compiler source code is also available under the MIT X11 License),[98] the runtime libraries under the GNU Lesser General Public License (LGPLv2 only) and the class libraries under the MIT License. These are all free software and open-source licenses and hence Mono is free and open-source software.

The license of the C# compiler was changed from the GPL to the MIT X11 license[99] to allow the compiler code to be reused in a few instances where the GPL would have prevented such:

  • Mono's Compiler as a Service
    • The Mono interactive Shell
    • The Mono embeddable C# compiler
  • Mono's implementation of the C# 4.0 dynamic binder.
  • MonoDevelop's built-in parser and AST graph

On March 18, 2016, Microsoft's acquisition of Xamarin was officially closed.[100] On March 31, 2016, Microsoft announced at Microsoft Build that they'll completely re-license Mono under the MIT License even in scenarios where previously a commercial license was necessary,[101] and Microsoft stated that they won't assert any "applicable patents" against parties that are "using, selling, offering for sale, importing, or distributing Mono."[102][103] It was also announced that Xamarin had contributed the Mono Project to the .NET Foundation.[102]

Mono and Microsoft's patents
Further information: Software patents and free software and Novell § Agreement with Microsoft

Mono's implementation of those components of the .NET stack not submitted to the ECMA for standardization has been the source of patent violation concerns for much of the life of the project.[104] In particular, discussion has taken place about whether Microsoft could destroy the Mono project through patent suits.[105] This discussion is now moot after Microsoft acquired Xamarin,[106] the primary maintainers of Mono. In June 2009 the Ubuntu Technical Board stated that it saw "no reason to exclude Mono or applications based upon it from the archive, or from the default installation set."[107]

The base technologies submitted to the ECMA, and therefore also the Unix/GNOME-specific parts, are claimed to be safe due to Microsoft's explicitly placing both ECMA 334 (C#) and ECMA 335 (CLI) standards under the Microsoft Community Promise. The concerns primarily relate to technologies developed by Microsoft on top of the .NET Framework, such as ASP.NET, ADO.NET and Windows Forms (see non-standardized namespaces), i.e. parts composing Mono's Windows compatibility stack. These technologies are today not fully implemented in Mono and not required for developing Mono-applications, they are simply there for developers and users who need full compatibility with the Windows system.

Should patent issues ever arise, the Mono project's stated strategy for dealing with them is as follows:[108]

  • Work around the patent by using a different implementation technique that retains the API, but changes the mechanism; if that is not possible, they would
  • Remove the pieces of code that were covered by those patents, and also
  • Find prior art that would render the patent useless.

Mono is also included in the list of software that the Open Invention Network has sworn to protect.[109]

On July 6, 2009, Microsoft announced that it was placing their ECMA 334 and ECMA 335 specifications under their Community Promise pledging that they would not assert their patents against anyone implementing, distributing, or using alternative implementations of .NET.[110] However, their position regarding the non-ECMA components like ASP.NET, ADO.NET, and Windows Forms (which are the bone of contention) remains unclarified.

The Free Software Foundation's Richard Stallman has stated in 2009-06-25 that "[...]we should discourage people from writing programs in C#. Therefore, we should not include C# implementations in the default installation of GNU/Linux distributions or in their principal ways of installing GNOME".[111] In 2009-07-16, Brett Smith (also from the FSF) stated that "Microsoft's patents are much more dangerous: it's the only major software company that has declared itself the enemy of GNU/Linux and stated its intention to attack our community with patents.", "C# represents a unique threat to us" and "The Community Promise does nothing to change any of this".[112]

Fedora Project Leader Paul Frields has stated, "We do have some serious concerns about Mono and we'll continue to look at it with our legal counsel to see what if any steps are needed on our part", yet "We haven't come to a legal conclusion that is pat enough for us to make the decision to take mono out".[113]

In November 2011 at an Ubuntu Developer Summit, developers voted to have the Mono-based Banshee media player removed from Ubuntu's default installation beginning on Ubuntu 12.04; although reported reasonings included performance issues on ARM architecture, blocking issues on its GTK+ 3 version, and it being, in their opinion, "not well maintained", speculation also surfaced that the decision was also influenced by a desire to remove Mono from the base distribution, as the remaining programs dependent on Mono, gbrainy and Tomboy, were also to be removed. Mono developer Joseph Michael Shields defended the performance of Banshee on ARM, and also the claims that Banshee was not well-maintained as being a "directed personal insult" to one of its major contributors.[114]

On March 31, 2016, Microsoft announced at Microsoft Build (following the previous acquisition of Xamarin[100]) that they will completely re-license Mono under the MIT license.[101] Microsoft issued the Patent Promise for Mono stating that they won't assert any "applicable patents" against parties that are "using, selling, offering for sale, importing, or distributing Mono".[102][103] It was also announced that Xamarin had contributed the Mono Project to the .NET Foundation.[102]

As of 2018 significant parts of Microsoft's own code for the .NET platform has been released under FOSS licenses, including the .NET Compiler Platform ("Roslyn"), ASP.NET, .NET Core, the .NET Micro Framework,[115] WinForms, WPF, and WinUI.[116]

Software developed with Mono
Banshee media player
GNOME Do

Many programs covering a range of applications have been developed using the Mono application programming interface (API) and C#. Some programs written for the Linux Desktop include Banshee, Beagle, F-Spot, Gbrainy, Docky/GNOME Do, MonoTorrent, Pinta, and Tomboy. The program, Logos 5 Bible Study Software (OS X Version), was written for the MacOS.

A number of video games, such as The Sims 3 and Second Life (for their scripting languages), OpenSimulator virtual world server, or games built with the Unity or MonoGame game engines, also make use of Mono.[117]

gollark: It's actually just interfaced to the backend for potatOS.
gollark: I'm not running any now, see.
gollark: Yes, it waits for my commands.
gollark: Also, I have the Haskell LLVM bindings working so none are safe.
gollark: Yes it does. I checked.

See also

References

Citations
  1. "releases: mono/mono".
  2. "FAQ: Licensing". Retrieved 3 July 2020.
  3. "Microsoft to acquire Xamarin and empower more developers to build apps on any device". Official Microsoft Blog. Retrieved 2016-02-24.
  4. "Mono Project aims to bring .Net apps to Linux". ZDNet. 2001-10-29. Called the Mono Project, this effort encompasses creating a development environment that will allow applications developed for .Net to run on Linux systems as well as at Windows systems. Mono originated out of a need for improved development tools for the GNOME community and for Ximian specifically, according to Miguel de Icaza, Ximian's chief technical officer.
  5. "Ximian's Mono project: .NET for monkeys, penguins, and gnomes". TechRepublic.
  6. "Mono Releases". Mono-project.com. Retrieved 2015-04-04.
  7. "OldReleases". Mono-project.com. Retrieved 2013-07-17.
  8. "Mono 1.0 Release Notes". Mono-project.com. Retrieved 2013-07-17.
  9. "Mono 1.1.1: Development Release". Mono-project.com. Retrieved 2013-07-17.
  10. "Mono 1.2: Release Notes". Mono-project.com. Retrieved 2013-07-17.
  11. "Release Notes Mono 2.0". Mono-project.com. 2008-10-06. Retrieved 2013-07-17.
  12. "Release Notes Mono 2.2". Mono-project.com. Retrieved 2013-07-17.
  13. "Linear IR - Mono". Mono-project.com. Retrieved 2013-07-17.
  14. "Mono's SIMD Support: Making Mono safe for Gaming - Miguel de Icaza". Tirania.org. 2008-11-03. Retrieved 2013-07-17.
  15. "Mono's C# Compiler as a Service on Windows. - Miguel de Icaza". Tirania.org. 2010-04-27. Retrieved 2013-07-17.
  16. "CsharpRepl - Mono". Mono-project.com. Retrieved 2013-07-17.
  17. "Release Notes Mono 2.4". Mono-project.com. Retrieved 2013-07-17.
  18. "Release Notes Mono 2.6". Mono-project.com. Retrieved 2013-07-17.
  19. "Release Notes Mono 2.8". Mono-project.com. Retrieved 2013-07-17.
  20. "Release Notes Mono 2.10". Mono-project.com. Retrieved 2013-07-17.
  21. "Release Notes Mono 3.0". Mono-project.com. Retrieved 2013-09-23.
  22. "Release Notes Mono 3.2". Mono-project.com. Retrieved 2013-09-23.
  23. "Release Notes Mono 3.4". Mono-project.com. Retrieved 2015-04-04.
  24. "Release Notes Mono 3.6". Mono-project.com. Retrieved 2015-04-04.
  25. "Release Notes Mono 3.8". Mono-project.com. Retrieved 2015-04-04.
  26. "Release Notes Mono 3.10". Mono-project.com. Retrieved 2015-04-04.
  27. "Release Notes Mono 3.12". Mono-project.com. Retrieved 2015-04-04.
  28. "Release Notes Mono 4.0". Mono-project.com. Retrieved 2015-05-03.
  29. "Release Notes Mono 5.0". Mono-project.com. Retrieved 2017-05-13.
  30. "Mono 5.2.0 Release Notes".
  31. "Mono 5.4.0 Release Notes".
  32. "Mono 5.8.0 Release Notes".
  33. "Mono 5.10.0 Release Notes".
  34. "Mono 5.12.0 Release Notes".
  35. "Mono 5.14.0 Release Notes".
  36. "Mono 5.16.0 Release Notes".
  37. "Mono 5.18.0 Release Notes".
  38. Bonisteel, Steven (June 23, 2000). "Microsoft sees nothing but .NET ahead". ZDNet. Archived from the original on November 5, 2011. Retrieved April 5, 2011.
  39. "ECMA-335-Part-I-IV - ECMA-335, 1st edition, December 2001" (PDF).
  40. Wilcox, Joe; Shankland, Stephen (June 28, 2001). "Microsoft edges into sharing code". ZDNet.
  41. "[Mono-list] Mono early history". 2003-10-13. Archived from the original on 2011-06-06. Retrieved 2005-03-30.
  42. "OSS .NET implementation Mono 1.0 released - Ars Technica". ArsTechnica. Retrieved 2009-10-23.
  43. "Supported Platforms". Mono website.
  44. Koep, Paul (2011-05-02). "Employees say hundreds laid off at Novell's Provo office". KSL-TV. Retrieved 2011-05-07.
  45. J. Vaughan-Nichols, Steven (2011-05-04). "Is Mono dead? Is Novell dying?". ZDNet. Retrieved 2011-05-07.
  46. Clarke, Gavin (2011-05-03). ".NET Android and iOS clones stripped by Attachmate". The Register. Retrieved 2011-05-07.
  47. "Announcing Xamarin - Miguel de Icaza". Tirania.org. 2011-05-16. Retrieved 2013-07-17.
  48. "The Death and Rebirth of Mono". infoq.com. 2011-05-17. Retrieved 2011-05-29. Even if they aren't supporting it, they do own a product that is in direct competition with Xamarin's future offerings. Without some sort of legal arrangement between Attachmate and Xamarin, the latter would face the daunting prospect of proving that their new development doesn't use any the technology that the old one did. Considering that this is really just a wrapper around the native API, it would be hard to prove you had a clean-room implementation even for a team that wasn't intimately familiar with Attachmate's code.
  49. "SUSE and Xamarin Partner to Accelerate Innovation and Support Mono Customers and Community". Novell. 2011-07-18. Retrieved 2011-07-18. The agreement grants Xamarin a broad, perpetual license to all intellectual property covering Mono, MonoTouch, Mono for Android and Mono Tools for Visual Studio. Xamarin will also provide technical support to SUSE customers using Mono-based products, and assume stewardship of the Mono open source community project.
  50. de Icaza, Miguel (2011-07-18). "Novell/Xamarin Partnership around Mono". Retrieved 2011-07-18.
  51. de Icaza, Miguel (2011-03-07). "GDC 2011". Retrieved 2011-03-11. We have no plans on building WPF. We just do not have the man power to build an implementation in any reasonable time-frame(...)For tools that are mostly OpenGL/DirectX based, use Windows.Forms, keeping in mind that some bug fixing or work around on their part might be needed as our Windows.Forms is not actively developed.
  52. "Mono compatibility list".
  53. "Mono Project Roadmap - Mono". Mono-project.com. Retrieved 2013-07-17.
  54. "MoonlightRoadmap". Mono Team. Retrieved 2008-11-08.
  55. "Releasing Moonlight 2, Roadmap to Moonlight 3 and 4 — Miguel de Icaza". Tirania.org. 2009-12-17. Retrieved 2013-07-17.
  56. "Moonlight 3.0 Preview 1 — Miguel de Icaza". Tirania.org. 2010-02-03. Retrieved 2013-07-17.
  57. "Xamarin abandons its Silverlight for Linux technology".
  58. "Ecma-335".
  59. "Technet.com". Archived from the original on 2013-06-22. Retrieved 2009-07-07.
  60. "Database Access - Mono".
  61. "Mono LLVM". Mono.
  62. "Compacting GC". mono-project.com. Retrieved 2008-12-16.
  63. Boehm, Hans-J. "Advantages and Disadvantages of Conservative Garbage Collection". Xerox PARC. Archived from the original on 2013-07-24. Retrieved 2008-12-16.
  64. ".NET Framework Architecture". official Mono documentation.
  65. de Icaza, Miguel. "Static Compilation in Mono".
  66. "Continuations - Mono".
  67. de Icaza, Miguel. "Monovation: Assembly Injection into Live Processes".
  68. "Supported Platforms - Mono".
  69. Narayanaswamy, Anand (23 Nov 2012). "Build Cross Platform Applications with Xwt". InfoQ. Archived from the original on 2016-04-15. Retrieved 2016-04-15.
  70. de Icaza, Miguel (22 February 2013). "The Making of Xamarin Studio". InfoQ. Archived from the original on 2016-04-15. Retrieved 2016-04-15.
  71. "Xwt Read Me". Xwt on GitHub. 15 Jan 2012. Archived from the original on 2016-04-16. Retrieved 2016-04-15.
  72. "DotGNU Project". Retrieved 2 June 2014.
  73. "FAQ". os.xamarin.com. 2011-08-01. MonoTouch is a commercial product based on the open source Mono project and is licensed on a per-developer basis.
  74. "Mono relicensed MIT". www.mono-project.com. 2016-03-31.
  75. "Xamarin for Everyone". blog.xamarin.com. 2016-03-31. we are announcing today our commitment to open source the Xamarin SDKs for Android, iOS, and Mac under the MIT license in the coming months
  76. de Icaza, Miguel. "MonoTouch 1.0 goes live".
  77. "MonoTouch 2.0.0". Xamarin.
  78. "MonoTouch 3.0.0". Xamarin.
  79. "MonoTouch 4.0.0". Xamarin.
  80. "MonoTouch 5.0". Xamarin.
  81. "MonoTouch 6.0". Xamarin.
  82. "Xamarin.iOS 6.2". Xamarin.
  83. "Xamarin.iOS 6.4". Xamarin.
  84. "MonoTouch and iPhone 4". Applications built with MonoTouch are native applications indistinguishable from other native applications.
  85. "Apple takes aim at Adobe… or Android?".
  86. "Statement by Apple on App Store Review Guidelines". Based on their input, today we are making some important changes to our iOS Developer Program license in sections 3.3.1, 3.3.2 and 3.3.9 to relax some restrictions we put in place earlier this year. In particular, we are relaxing all restrictions on the development tools used to create iOS apps, as long as the resulting apps do not download any code. This should give developers the flexibility they want, while preserving the security we need.
  87. "Great News for MonoTouch Users". With these new terms, the ambiguity is gone and C# lovers and enthusiasts can go back to using MonoTouch. Developers that like garbage collection and their strongly typed languages can resume their work.
  88. "How is Mono for Android licensed?". Mono for Android FAQ. 2011-08-28. Retrieved 2012-03-29.
  89. "Novell's Mono project bringing .Net development to Android". NetworkWorld.
  90. "Novell's Mono project bringing .Net development to Android". InfoWorld.
  91. "MonoDroid: .NET Support Coming to Android". TechieBuzz.
  92. "Mono for Android brings C# to Android". Heise Online. 2011-04-07. Retrieved 2011-04-07.
  93. "Novell (Mono/C#) is developing MonoDroid". Android Community. This will make it easier for developers to make cross platform apps as well as bring some of the existing apps that are made using MonoTouch to Android.
  94. "Mono for Android". H-Online. Our vision is to allow developers to reuse their engine and business logic code across all mobile platforms and swapping out the user interface code for a platform-specific API.
  95. "Microsoft won't stop (Mono) .NET on Android". TechWorld. The type of action Oracle is taking against Google over Java is not going to happen. If a .NET port to Android was through Mono it would fall under the Microsoft Community Promise Agreement.
  96. "Microsoft says .NET on Android is safe, no litigation like Oracle". Developer Fusion.
  97. "Xamarin Designer for Android". Visual Studio Magazine. On May 14, Xamarin announced Mono for Android 4.2.
  98. "Mono C# Compiler Under MIT X11 License". Novell Inc. 2008-04-08. Archived from the original on 2008-05-13. Retrieved 2008-04-09.
  99. de Icaza, Miguel. "Mono C# compiler now also MIT X11 licensed".
  100. "Xamarin for Everyone". Xamarin Blog. Xamarin. 31 March 2016. Archived from the original on 2016-04-12. Retrieved 2016-04-12.
  101. Anderson, Tim (31 March 2016). "Microsoft to make Xamarin tools and code free and open-source". The Register.
  102. Ferraira, Bruno (31 March 2016). "Xamarin now comes free with Visual Studio". The Tech Report.
  103. "Microsoft Patent Promise for Mono". Mono on GitHub. Mono Project. 2016-03-28. Archived from the original on 2016-04-12. Retrieved 2016-04-12.
  104. Babcock, Charles (August 7, 2001). "Will open source get snagged in .Net?". ZDNet Asia.
  105. Smith, Brett (July 16, 2009). "Microsoft's Empty Promise". fsf.org.
  106. https://blog.xamarin.com/a-xamarin-microsoft-future/
  107. "Mono Position Statement". Canonical Ltd. It is common practice in the software industry to register patents as protection against litigation, rather than as an intent to litigate. Thus mere existence of a patent, without a claim of infringement, is not sufficient reason to warrant exclusion from the Ubuntu Project.
  108. "Mono FAQ: Licensing | Patents".
  109. "How Mono got into Fedora". Linux Weekly News. The list of "certain Linux-related applications" is said to exist, though it has not, yet, been posted publicly. But Mono is apparently on that list. So anybody who files patent infringement suits against Mono users, and who is, in turn, making use of technology covered by OIN's patents is setting himself up for a countersuit. Depending on the value of the patents held by OIN, that threat could raise the risk of attacking Mono considerably.
  110. "The ECMA C# and CLI Standards". Port 25. 2009-07-06. Archived from the original on 2013-06-22. Retrieved 2009-07-07. Under the Community Promise, Microsoft provides assurance that it will not assert its Necessary Claims against anyone who makes, uses, sells, offers for sale, imports, or distributes any Covered Implementation under any type of development or distribution model, including open-source licensing models such as the LGPL or GPL.
  111. "Why free software shouldn't depend on Mono or C#".
  112. "Microsoft's Empty Promise".
  113. "Fedora is concerned about Mono". internetnews.com. 2009-06-12. Retrieved 2010-07-04. We haven't come to a legal conclusion that is pat enough for us to make the decision to take mono out
  114. "'Bansheegeddon' may see Banshee, Mono dropped from Ubuntu default". ITWorld. Retrieved 31 August 2015.
  115. Landwerth, Immo (12 November 2014). ".NET Core is Open Source". .NET Framework Blog. Microsoft. Retrieved 30 December 2014.
  116. https://www.hanselman.com/blog/AnnouncingWPFWinFormsAndWinUIAreGoingOpenSource.aspx
  117. "Companies using Mono". Mono-project. Mono-project. Retrieved 30 August 2015.

Sources
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.