Bt Mono Latest Version

[Hedvig Horning]

Ive had some experience with .NET Core but I've never used mono before. So I installed mono on a machine running Ubuntu 20.04 but I cannot find the dotnet version that it will be used (since I must use 4.7.2).

It sounds like this might be the first time you are using Mono. If so, watch out. Mono is far from 100% compatible with .NET Framework. There are missing features, bugs, performance issues and so on. It works for many use-cases, but it's not really supported by Microsoft.

The package referenceassemblies-pcl should be installed for PCL compilation support - this will resolve most cases of "Framework not installed: .NETPortable" errors during software compilation.

Mono on Linux before 3.12 by default didn't trust any SSL certificates so you got errors when accessing HTTPS resources. This is not required anymore as 3.12 and later include a new tool that runs on package installation and syncs Mono's certificate store with the system certificate store (on older versions you had to import Mozilla's list of trusted certificates by running mozroots --import --sync). Some systems are configured in a way so that the necessary package isn't pulled in when Mono is installed, in those cases make sure the ca-certificates-mono package is installed.

All other version tags are still available, but won't get those updates so you need to keep your images up to date by running apt update yourself. We encourage you to move to latest Mono releases as soon as they're available.

2: as you said, the mono version supports C#. That is the core difference. The standard version supports godot own scripting language, gdscript, so you can still write scripts and do everything you would be able to do in the mono version.

E.g., does Unity 2018.3 come with 5.16.0? Would be nice to be able to use the 32bit floating math and the Span with the intrinsics based implementation. Or will I have to wait for later versions of Unity?

There is not a direct mapping between Unity versions and Mono versions, since we pull the Mono source code and modify it. Unity does support specific .NET profile versions though. In Unity 2018.3, you can choose either .NET 4.7.1 or .NET Standard 2.0. Unfortunately Span is not available in either.

In a future version of Unity we do plan to support .NET Standard 2.1, where Span is available. You can follow the development of .NET Standard here: GitHub - dotnet/standard: This repo is building the .NET Standard

I noticed that one of the Unity Packages I installed is referencing a different System.Runtime.CompilerServices.Unsafe.dll:

F:/projects/Ironbyte.Unity/Library/PackageCache/com.unity....@0.0.9-preview.10/System.Runtime.CompilerServices.Unsafe.dll

TargetFramework seems to be set to 4.7.1 in that file.

I just installed 4.8 Developer Pack, and the DotNet 5.0 SDK, but making a new project still targets it at 4.7.1.

Changing that setting to 4.8 also does nothing it seems.

Not even sure what value is supposed to be there to make this work

Mono is a free and open-source .NET Framework-compatible software framework. Originally by Ximian, it was later acquired by Novell, and is now being led by Xamarin, a subsidiary of Microsoft[4] and the .NET Foundation. Mono can be run on many software systems.

When Microsoft first announced their .NET Framework in June 2000 it was described as "a new platform based on Internet standards",[5] and in December of that year the underlying Common Language Infrastructure was published as an open standard, "ECMA-335",[6] opening up the potential for independent implementations.[7] Miguel de Icaza of Ximian believed that .NET had the potential to increase programmer productivity and began investigating whether a Linux version was feasible.[8] 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 of development, Mono 1.0 was released on June 30, 2004.[9] 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.[10]

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

On May 16, 2011, 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.[14] 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.[15] 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.[16][17]

Mono's current version is 6.12.0 (as of June 2024[update]). 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.[18] 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.

As of January 14, 2021, Mono has full support for all the features in .NET 4.7 except Windows Presentation Foundation (WPF) (which the Mono team do not plan to support due to the amount of work it would need)[18] and Windows Workflow Foundation (WF), and with only limited support for Windows Communication Foundation (WCF) and the ASP.NET async stack. However, System.Web and WCF are candidates for 'almost immediate' porting from the .NET reference source back to Mono.[19] Some missing parts of the .NET Framework are under development in an experimental Mono subproject called Olive.[20]

An open-source implementation of Microsoft Silverlight, called Moonlight, has been included since Mono 1.9.[21] 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.[22] A preview release of Moonlight 3.0 was announced in February 2010 and contains updates to Silverlight 3 support.[23]

The Moonlight project was abandoned on May 29, 2012.[24] 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.

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,[25] 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.[26]

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.[27]

3a8082e126