Thanks to feedbacks garnered since the .NET 4.x Equivalent scripting runtime became supported in Unity 2018.1, improvements have been made in terms of bug fixes. Moreover, additional features have also been added which is only viable with the .NET 4.x Equivalent scripting runtime.
As part of the new update, Unity Labs introduced managed code debugging to the IL2CPP scripting backend with the same features as the MONO scripting backend.
Unity also added full TLS 1.2 support to all of the .NET class library APIs, on all Unity platforms with Mono and IL2CPP which means Unity will run correctly with the operating system to access local certificate store and make secure socket and HTTPS connections work.
Additionally, The API Compatibility Levels available with the .NET 4.x Equivalent scripting runtime bring lots of great .NET APIs. They also bring more code from the .NET class libraries, which can increase the build size. They aim to focus primarily in making the build size as small as possible for the .NET 4.x Equivalent scripting runtime on both Unity 2018.2 and the upcoming 2018.3.
Users can expect Unity 2018.3 will make .NET 4.x Equivalent as the default for future projects.
Darryl Laurance is an intern over at IGN Southeast Asia who loves survival horror and action RPGs.
