and .NET, what’s next?

on YouTube ↗30m

" summary

Unity moves from Mono/.NET Framework to a CoreCLR-based runtime while keeping IL2CPP for AOT, ships .NET Standard 2.1 support and a selectable coreclr scripting backend for standalone players, and plans to replace the editor JIT with CoreCLR. Tooling switches to MSBuild and SDK-style projects with automatic asmdef → csproj translation and NuGet (UPM still works but NuGet cannot depend on UPM). Engineers implement the Mono embedding API on CoreCLR with a custom marshaling layer using GCHandles, add mixed-mode debugging, and introduce awaitable coroutine async/await support.

AI-written summary · about

" chapters (7)

1. 0:00.NET and Unity's future
2. 3:57.NET strategy for Unity
3. 6:47Modernizing .NET workflow
4. 10:15Transitioning to .NET Core
5. 16:55Core CLR scripting backend
6. 18:58Async/await in Unity runtime
7. 21:24Q&A on .NET and Unity

" related talks

• 53mCSharpify Your Engine: A Guide to Embedding C#Andreia Gaita · JetBrains GameDev Days 2024
• 56m.NET 5: runtimesEgor Bogatov · DotNext 2019 Moscow
• 51m.NET and WebAssembly: Back to the browser?Larry Ewing · Update Conference Prague 2019
• 56mUnity for the enterprise developerMatt Ellis · NDC Sydney 2019
• 01h 04mWhat is new in .NET 6 and the future of .NETJohnny Hooyberghs · Update Conference Prague 2021
• 01h 15mPanel discussion on the future of .NETMads Torgersen, Mark Rendle, Tess Ferrandez-Norlander, Bryan Hogan, Oren Novotny · NDC London 2019
• 54mThe History of .NETRichard Campbell · NDC Sydney 2017
• 01h 09mThe History of .NETRichard Campbell · NDC London 2018