3 ms·
I am not sure about the end of the journey. Lots of legacy .NET Framework code means I will continue targeting .NET Standard 2.0. That's why nobody used 2.1 - i
by lostmsu 6y ago
I am not sure about the end of the journey. Lots of legacy .NET Framework code means I will continue targeting .NET Standard 2.0. That's why nobody used 2.1 - it did not support legacy framework. .NET 5 does not solve this problem. Just renaming .NET Core (3+1) to .NET 5 won't magically make legacy code portable.
Also, there is still very popular Unity 3D, that can target later framework, but will continue to run on the legacy one itself for a while.
- WorldMaker 6y agoMy understanding is that Unity is hoping to catch up as soon as some of the final AOT stuff merges from Mono into .NET 6, so "for a while" in the case of Unity is now supposed to be a year or less (given Preview versions).
- pjmlp 6y agoUnity already has their own AOT, two implementations actually.