![]() NET development ecosystem, more than 100 comments were appended to the post, many going into great detail about technical issues and more broad comments, such as this one about Visual Studio integration: Speaking to the popularity of Unity in the. We have done work to use Assembly Load Context instead, but that will be a breaking change, and will require time to implement properly, both from the Unity side and in user projects. NET Core ecosystem does not support domain reloading, which is a fundamental requirement of the Unity Editor. NET Framework ecosystem will not work, and must be recompiled. Any assemblies compiled against mscorlib.dll from the. This is a breaking change for all Unity users.NET 5 entirely." He described the biggest hurdles for this as: NET 6 ships in November as a long-term support (LTS) release, meaning that "Unity will likely skip. NET 6 support: Peterson described this as "still a bit fuzzy," with the company hoping to provide a preview around the time the landmark, unifying, milestone. This will bring full C# 9 support to Unity users as well." Complete C# 9 support: "We'd like to have covariant return type support in Mono and IL2CPP for Unity 2021.2.NET Standard support along with the latest Mono code that features default interface methods support. Complete C# 8 support: This comes with the aforementioned.NET Standard 2.1, Mono's class libraries do support it, so we should be able to provide a nice bridge to a. ![]() NET Standard 2.1 support to Unity's existing. NET Standard 2.1: This will expose user-requested APIs such as Span and ranges. NET Core class library implementation, including many changes to the way the class library code interacts with platform-specific code.
0 Comments
Leave a Reply. |