Home/ Questions/Q 992121
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-16T06:12:54+00:00

I know the converse is not true, but if my application works using Mono

  • 0

I know the converse is not true, but if my application works using Mono is it guaranteed to work if I switch to the real deal? If not, where can I find a list of caveats?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Both Mono and .NET are supersets of the ECMA/ISO CLI family of specifications. However, neither .NET nor Mono are subsets of the other. Both Mono and .NET add features on top of ECMA/ISO CLI, but while Mono implements many of .NET’s additions, .NET does not implement any of Mono’s additions.

    Here’s a few examples:

    • Mono has larger arrays. This is actually not an added feature to the ECMA/ISO CLI specification but an optional one: the specification says that array indices must be either 32 bit or 64 bit. .NET chose 32 bit but Mono chose 64, since arrays with 10 billion entries and more are quite common in supercomputing applications, where Mono has quite a strong market share. So, if your app has an array with several billions of entries, it will run just fine on Mono but won’t work on .NET.
    • Mono has continuations built into the VM. These are important for game programming.
    • Mono has native SIMD support for parallel operations on arrays, which are mapped to native CPU SIMD instructions (MMX, SSE, VMX).
    • Mono has compiler-as-a-service, which Microsoft has been only vaguely talking about for some unspecified future version of .NET.
    • Mono has a lot of additional libraries, especially bindings to graphics libraries other than Windows Forms (wx.NET, Gtk#, Cocoa#, …)

    Note, however, that (except for the arrays), all of these are clearly distinguishible by their namespaces, since none of them live in the System or Microsoft namespaces.

    EDIT: Actually, most of the above-mentioned extensions are explicitly designed to also work on .NET. For example, Mono.Simd also runs on .NET, but without the runtime support that the Mono VM has, it’s unusably slow. (Basically, all the SIMD operations are implemented in C#, but the Mono compiler detects those calls and replaces them with their corresponding assembly instructions. That way, they work on .NET, but without the special treatment, they are significantly slower.) Also, the C# REPL is currently being re-implemented on top of Reflection.Emit (at the moment, it calls the Mono compiler directly), so that it will work on .NET in the future. Gtk# works just fine on Windows and .NET.

    Only the Mono.Tasklet library cannot be implemented on .NET, since it requires VM-level support for continuations.

    • 0