Is the old Mono Compatibility Matrix a solid reference to use when looking at what .NET functions are supported for our use in Unity, or is there something more up to date that I could reference?
Ignore what I have to say if you’re using Unity 5.5 beta and plan to move forward with even newer versions. Unity has finally released updated compilers for mono, and will have more to come, expanding the compatibility set.
Anyways…
Unity has been using the same old mono runtime for years. It’s extremely outdated, and a really early version with many flaws to it.
With that said… because they haven’t changed it in ages, that support matrix is still applicable, since no changes have been made to expand it.
I noticed they updated the compiler, but my understanding is that they haven’t expanded the .NET compatibility yet. Did I miss something?
If we’re going to talk about 5.5 beta, then things are different.
Yes, currently they’ve only updated the compiler, so technically the compatability list is the same. But it’s only a beta right now and shouldn’t be used for regular development. And since they have plans to further upgrade stuff, the .Net compatability list may expand.
This beta status, and potential to grow as newer versions come out is why I mentioned 5.5.
The short answer is, compatability list can be used to determine as of today.
As time goes on, it’s going to change though… and we’re currently right at that turning point.