|This article is outdated. (March 2016)|
|Developer(s)||Xamarin, Microsoft (formerly by Novell, originally by Ximian), and the Mono community|
|Initial release||June 30, 2004|
|Stable release||4.4.0 / June 8, 2016|
|Written in||C, C#, XML|
|Operating system||Windows, OS X, Linux|
|Platform||x86-64, x86, ARM, MIPS, PowerPC, SPARC, S390, IA-64|
|License||MIT, LGPLv2 and GPLv2, or dual license|
Mono is a free and open source project led by Xamarin, a subsidiary of Microsoft (formerly by Novell and originally by Ximian) to create an Ecma standard-compliant, .NET Framework-compatible set of tools including, among others, a C# compiler and a Common Language Runtime. The logo of Mono is a stylized monkey's face, mono being Spanish for monkey.
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. Mono can be run on many software systems including Android, most Linux distributions, BSD, OS X, Windows, Solaris, and even some game consoles such as PlayStation 3, Wii, and Xbox 360.
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's "Open Specification Promise"—a covenant stating that Microsoft would 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 (see below).
- 1 History
- 2 Current status and roadmap
- 3 Mono components
- 4 Framework architecture
- 5 MonoDevelop
- 6 Xamarin.iOS and Xamarin.Android
- 7 License
- 8 Mono and Microsoft's patents
- 9 Software developed with Mono
- 10 See also
- 11 References
- 12 External links
|2004-06-30||1.0||C# 1.0 support|
|2006-11-09||1.2||C# 2.0 support|
|2008-10-06||2.0||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-13||2.2||Mono switches its JIT engine to a new internal representation that gives it a performance boost and introduces SIMD support in the Mono.Simd 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 and the C# Interactive Shell (C# REPL)
|2009-03-30||2.4||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-15||2.6||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-22||2.8||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|
|2012-10-18||3.0||C# 5.0 support, async support, Async Base Class Library Upgrade and MVC4 - Partial, no async features support.|
|2013-07-24||3.2||Default Garbage Collector is now the SGEN, instead of Boehm|
|2015-04-29||4.0||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|
When Microsoft first announced their .NET Framework in June 2000 it was described as "a new platform based on Internet standards", and in December of that year the underlying Common Language Infrastructure was published as an open standard, "ECMA-335", opening up the potential for independent implementations. Miguel de Icaza of Ximian believed that .NET had the potential to increase programmer productivity and began investigating whether a Linux version was feasible. 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. 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.
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 commercial .NET stacks for iOS and Android from scratch, because Novell still owned MonoTouch and Mono for Android at the time. 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. 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.
Current status and roadmap
Mono's current version is 4.0.0 (as of May 2015[update]). This version provides the core API of the .NET Framework and support for Visual Basic.NET and C# versions 2.0, 3.0, and 4.0. LINQ to Objects, XML, and SQL are part of the distribution. C# 6.0 is now the default mode of operation for the C# compiler. Windows Forms 2.0 is also supported, but not actively developed, and as such its support on Mono is incomplete. Version 4.0 is 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), Windows Workflow Foundation (WF), limited Windows Communication Foundation (WCF). Some missing parts of the .NET Framework are under development in an experimental Mono subproject called Olive.
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.
An open source implementation of Microsoft Silverlight, called Moonlight, has been included since Mono 1.9. 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. A preview release of Moonlight 3.0 was announced in February 2010 and contains updates to Silverlight 3 support.
The Moonlight project was abandoned on May 29, 2012. 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.
Mono consists of three groups of components:
- Core components
- Mono/Linux/GNOME development stack
- 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, 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.
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.
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.
The major components of Mono include:
- Code Execution Engine
- Class Libraries
- Base Class Library
- .NET Compatibility Class Libraries
- Mono specific class libraries:
- Cross platform class libraries for both Mono and .NET (Gtk#, Mono.Cecil, Mono.CSharp, Text.Templating)
- Unix-specific class libraries (POSIX, Filesystem in Userspace (FUSE), curses)
- Platform-specific class libraries (bindings for: Mac, iOS, Android, MeeGo)
- CLI Assemblies
- CLI Metadata
- Mono's Common Language Runtime
- Mono-specific enhancements
- Native interop services and COM interop
- Security - Transparent Code Framework
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
--nollvm command line arguments, and it defaults to the fast Mono code generation engine.
The default garbage collector prior to Mono 3.1.1 (the Boehm-Demers-Weiser Conservative Garbage Collector), has significant limitations compared to commercial garbage-collected runtimes like the Java Virtual Machine or the .NET framework's runtime. Because the garbage collector can exhibit memory leaks on certain classes of applications, it may be unsuitable for long-running server applications.
As of October 2010[update], 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. 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.
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.
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), or more commonly known as the Common Language Runtime, is implemented by the Mono executable. The runtime is used to execute compiled .NET applications. The common language infrastructure is defined by the ECMA standard. 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 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).
- C# Interactive Shell.
- SIMD support 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 (used on Mono/iPhone, Mono/PS3).
- Mono coroutines (used to implement micro-threading code and continuations, mostly for game developers).
- Assembly injection to live processes.
- 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.
Windows XP, Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows 10, MacOSX or Linux
Several projects extend Mono and allow developers to use it in their development environment. These projects include:
- Banshee Media Player 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 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.
- 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, 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, 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.
Mac OS X:
- Cocoa# – wrappers around the native OS X toolkit (Cocoa) (deprecated).
- Monobjc – a set of bindings for OS X programming.
- MonoMac – newer bindings for OS X programming, based on the MonoTouch API design.
- 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.
- MonoTools for Visual Studio A Visual Studio plugin that allows Windows developers to target Linux and Mac OS X right from Visual Studio and integrates with SUSE Studio.
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).
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, Java, 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, after Microsoft's acquisition of Xamarin in 2016, the Mono runtime itself was relicensed under MIT license and both Xamarin.iOS and Xamarin.Android are being made free and open source.
|2009-09-14||MonoTouch 1.0||Initial release|
|2010-04-05||MonoTouch 2.0||iPad support|
|2010-04-16||MonoTouch 3.0||iPhone 4 support|
|2011-04-06||MonoTouch 4.0||iOS 4 support|
|2011-10-12||MonoTouch 5.0||iOS 5 support|
|2012-09-19||MonoTouch 6.0||iOS 6 support|
|2013-02-20||Xamarin.iOS 6.2||Visual Studio support|
|2013-07-24||Xamarin.iOS 6.4||.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. 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:
- 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. 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.
Xamarin.Android (formerly known as Mono for Android), initially developed by Novell and continued by Xamarin, is a proprietary implementation of Mono for Android-based smart-phones. It was first released on April 6, 2011. Mono for Android was developed to allow developers to more easily write cross-platform applications that will run on all mobile platforms. 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."
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."
The Xamarin.Android stack consists of the following components:
- Mono runtime
- An Android UI designer
- 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.
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 will also be available under the MIT X11 License), 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 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. 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, and Microsoft stated that they won't assert any "applicable patents" against parties that are "using, selling, offering for sale, importing, or distributing Mono."  It was also announced that the Mono Project was contributed to the .NET Foundation.
Mono and Microsoft's patents
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. In particular, discussion has taken place about whether Microsoft could destroy the Mono project through patent suits. This discussion is now moot after Microsoft acquired Xamarin, 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."
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[when?] 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:
- 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.
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. 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". 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".
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".
In November 2011 at a 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.
On March 31, 2016 Microsoft announced at Microsoft Build (following the previous acquisition of Xamarin) that they will completely re-license Mono under the MIT license. 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". It was also announced that the Mono Project was contributed to the .NET Foundation. These developments cancel many of the previous patent violation concerns related to the Mono project. They seem to be a logical continuation of the Microsoft's shift towards more supportive attitude to open software, which has begun by open sourcing the .NET Compiler Platform ("Roslyn") and the ASP.NET on April 2014, and later the .NET Core (open sourced on November 2014) and other software.
Software developed with Mono
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, Docky, F-Spot, Gbrainy, GNOME Do, MonoTorrent, Pinta, and Tomboy.
A number of video games, such as The Sims 3 and Second Life's for their scripting languages, OpenSimulator virtual world server, or games built with the Unity or MonoGame game engines, also make use of Mono.
- Common Language Runtime
- .NET Framework
- .NET standard libraries
- Base Class Library (BCL)
- List of .NET libraries and frameworks
- .NET Core, an open source framework similar to .NET.
- Comparison of application virtual machines
- DotGNU – A free software umbrella project which includes Portable.NET
- MonoDevelop – An open source IDE targeting both Mono and Microsoft .NET framework platforms
- Moonlight (runtime), an open source implementation of Microsoft's Silverlight developed by the Mono Project
- Shared Source Common Language Infrastructure – Microsoft's shared source implementation of .NET, formerly codenamed Rotor
- mod_mono – A module for the Apache HTTP Server that allows for hosting of ASP.NET pages and other assemblies on multiple platforms by use of Mono
- "Mono download page". mono-project.com. Retrieved 2015-12-21.
- "Release Notes Mono 4.2.1". mono-project.com. Retrieved 2015-12-21.
- "FAQ: Licensing – Mono". Retrieved 2009-11-26.
- "Microsoft to acquire Xamarin and empower more developers to build apps on any device". Official Microsoft Blog. Retrieved 2016-02-24.
- "Ximian's Mono project: .NET for monkeys, penguins, and gnomes". TechRepublic. Archived from the original on 2016-04-10.
- "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.
- "Mono Releases - Mono". Mono-project.com. Retrieved 2015-04-04.
- "OldReleases - Mono". Mono-project.com. Retrieved 2013-07-17.
- "Mono 1.0 Release Notes". Go-mono.com. Retrieved 2013-07-17.
- "Mono 1.1.1: Development Release: Features and Known Issues". Go-mono.com. Retrieved 2013-07-17.
- "Mono 1.2: Release Notes". Go-mono.com. Retrieved 2013-07-17.
- "Release Notes Mono 2.0 - Mono". Mono-project.com. 2008-10-06. Retrieved 2013-07-17.
- "Release Notes Mono 2.2 - Mono". Mono-project.com. Retrieved 2013-07-17.
- "Linear IR - Mono". Mono-project.com. Retrieved 2013-07-17.
- "Mono's SIMD Support: Making Mono safe for Gaming - Miguel de Icaza". Tirania.org. 2008-11-03. Retrieved 2013-07-17.
- "Mono's C# Compiler as a Service on Windows. - Miguel de Icaza". Tirania.org. 2010-04-27. Retrieved 2013-07-17.
- "CsharpRepl - Mono". Mono-project.com. Retrieved 2013-07-17.
- "Release Notes Mono 2.4 - Mono". Mono-project.com. Retrieved 2013-07-17.
- "Release Notes Mono 2.6 - Mono". Mono-project.com. Retrieved 2013-07-17.
- "Release Notes Mono 2.8 - Mono". Mono-project.com. Retrieved 2013-07-17.
- "Release Notes Mono 2.10 - Mono". Mono-project.com. Retrieved 2013-07-17.
- "Release Notes Mono 3.0". Mono-project.com. Retrieved 2013-09-23.
- "Release Notes Mono 3.2". Mono-project.com. Retrieved 2013-09-23.
- "Release Notes Mono 3.4". Mono-project.com. Retrieved 2015-04-04.
- "Release Notes Mono 3.6". Mono-project.com. Retrieved 2015-04-04.
- "Release Notes Mono 3.8". Mono-project.com. Retrieved 2015-04-04.
- "Release Notes Mono 3.10". Mono-project.com. Retrieved 2015-04-04.
- "Release Notes Mono 3.12". Mono-project.com. Retrieved 2015-04-04.
- "Release Notes Mono 4.0". Mono-project.com. Retrieved 2015-05-03.
- Bonisteel, Steven (June 23, 2000). "Microsoft sees nothing but .NET ahead". ZDNet.
- "ECMA-335-Part-I-IV - ECMA-335, 1st edition, December 2001" (PDF).
- Wilcox, Joe; Shankland, Stephen (June 28, 2001). "Microsoft edges into sharing code". ZDNet.
- "[Mono-list] Mono early history.". 2003-10-13. Archived from the original on 2014-01-27.
- "OSS .NET implementation Mono 1.0 released - Ars Technica". ArsTechnica. Retrieved 2009-10-23.
- "Supported Platforms". Mono website.
- Koep, Paul (2011-05-02). "Employees say hundreds laid off at Novell's Provo office". KSL-TV. Retrieved 2011-05-07.
- J. Vaughan-Nichols, Steven (2011-05-04). "Is Mono dead? Is Novell dying?". ZDNet. Retrieved 2011-05-07.
- Clarke, Gavin (2011-05-03). ".NET Android and iOS clones stripped by Attachmate". The Register. Retrieved 2011-05-07.
- "Announcing Xamarin - Miguel de Icaza". Tirania.org. 2011-05-16. Retrieved 2013-07-17.
- "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.
- "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.
- de Icaza, Miguel (2011-07-18). "Novell/Xamarin Partnership around Mono". Retrieved 2011-07-18.
- 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.
- "Mono compatibility list".
- "Mono Project Roadmap - Mono". Mono-project.com. Retrieved 2013-07-17.
- "MoonlightRoadmap". Mono Team. Retrieved 2008-11-08.
- "Releasing Moonlight 2, Roadmap to Moonlight 3 and 4 — Miguel de Icaza". Tirania.org. 2009-12-17. Retrieved 2013-07-17.
- "Moonlight 3.0 Preview 1 — Miguel de Icaza". Tirania.org. 2010-02-03. Retrieved 2013-07-17.
- "Xamarin abandons its Silverlight for Linux technology".
- "Database Access - Mono".
- "Compacting GC". mono-project.com. Retrieved 2008-12-16.
- Boehm, Hans-J. "Advantages and Disadvantages of Conservative Garbage Collection". Xerox PARC. Retrieved 2008-12-16.
- ".NET Framework Architecture". official Mono documentation.
- de Icaza, Miguel. "Static Compilation in Mono".
- "Continuations - Mono".
- de Icaza, Miguel. "Monovation: Assembly Injection into Live Processes".
- "Supported Platforms - Mono".
- "DotGNU Project". Retrieved 2 June 2014.
- "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.
- "Mono relicensed MIT". www.mono-project.com. 2016-03-31.
- "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
- de Icaza, Miguel. "MonoTouch 1.0 goes live.".
- "MonoTouch 2.0.0". Xamarin.
- "MonoTouch 3.0.0". Xamarin.
- "MonoTouch 4.0.0". Xamarin.
- "MonoTouch 5.0". Xamarin.
- "MonoTouch 6.0". Xamarin.
- "Xamarin.iOS 6.2". Xamarin.
- "Xamarin.iOS 6.4". Xamarin.
- "MonoTouch and iPhone 4".
Applications built with MonoTouch are native applications indistinguishable from other native applications.
- "Apple takes aim at Adobe… or Android?".
- "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.
- "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.
- "How is Mono for Android licensed?". Mono for Android FAQ. 2011-08-28. Retrieved 2012-03-29.
- "Novell's Mono project bringing .Net development to Android". NtworkWorld.
- "Novell's Mono project bringing .Net development to Android". InfoWorld.
- "MonoDroid: .NET Support Coming to Android". TechieBuzz.
- "Mono for Android brings C# to Android". Heise Online. 2011-04-07. Retrieved 2011-04-07.
- "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.
- "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.
- "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.
- "Microsoft says .NET on Android is safe, no litigation like Oracle". Developer Fusion.
- "Xamarin Designer for Android". Visual Studio Magazine.
On May 14, Xamarin announced Mono for Android 4.2.
- "Mono C# Compiler Under MIT X11 License". Novell Inc. 2008-04-08.
- de Icaza, Miguel. "Mono C# compiler now also MIT X11 licensed".
- "Xamarin for Everyone". Xamarin Blog. Xamarin. 31 March 2016. Archived from the original on 2016-04-12. Retrieved 2016-04-12.
- Anderson, Tim (31 March 2016). "Microsoft to make Xamarin tools and code free and open source.". The Register.
- Ferraira, Bruno (31 March 2016). "Xamarin now comes free with Visual Studio.". The Tech Report.
- "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.
- Babcock, Charles (August 7, 2001). "Will open source get snagged in .Net?". ZDNet Asia.
- Smith, Brett (July 16, 2009). "Microsoft's Empty Promise". fsf.org.
- "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.
- "Mono FAQ: Licensing | Patents".
- "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.
- "The ECMA C# and CLI Standards". Port 25. 2009-07-06.
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.
- "Why free software shouldn't depend on Mono or C#".
- "Microsoft's Empty Promise".
- "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
- "'Bansheegeddon' may see Banshee, Mono dropped from Ubuntu default". ITWorld. Retrieved 31 August 2015.
- Landwerth, Immo (12 November 2014). ".NET Core is Open Source". .NET Framework Blog. Microsoft. Retrieved 30 December 2014.
- "Companies using Mono". Mono-project. Mono-project. Retrieved 30 August 2015.
- This article incorporates text from Mono's homepage, which was then under the GNU Free Documentation License.
- de Icaza, Miguel (October 13, 2003). "[Mono-list] Mono early history." (mailing list). Retrieved December 6, 2005.
- Dumbill, Edd (March 11, 2004). "Will Mono Become the Preferred Platform for Linux Development?". ONLamp. Retrieved October 14, 2006.
- Loli-Queru, Eugenia (February 22, 2005). "Mono Applications? Aplenty!". OSNews. Retrieved December 6, 2005.
- Kerner, Sean Michael (November 18, 2005). "Mono Project Goes Virtual". Internet News. Retrieved October 14, 2006.
- Kerner, Sean Michael (November 9, 2006). "Months Late, Novell Ships Mono 1.2". internetnews.com.
- Northcutt, Corey (October 12, 2006). "In the World of mod_mono". Ubiquity. Archived from the original on February 23, 2007. Retrieved October 14, 2006.
- Campbell, Sean (October 8, 2008). "Interview with Joseph Hill - Product Manager - Mono - Novell". HSIB. Retrieved October 8, 2008.
- Smith, Tim (September 9, 2010). "A Brief Introduction to the Java and .NET Patent Issues". InfoQ. Retrieved September 13, 2010.