Replies: 7 comments 1 reply
|
For me .NET Native should be deleted to be replaced by .NET 5 |
|
The only way .Net Native should survive is if it's available to .Net 5. Are we going to reunite or what? Or are we going to still be in the same situation in 2 years time as we are now, using all these different frameworks and all complaining about how support is lacking for the particular variant we are stuck on. Lets get this sorted .. .Net 5 and choose JIT or AOT at config. done. |
|
AOT/precompilation support should be opt-in and made available in v5.
Now obviously .NET Core 4 materialized into .NET 5 but this makes me think it's on the burner for sooner or later. |
The pandemic interfered with the roadmap, so it would likely be in .NET 6 |
|
when will .NET 5 official support arrive?MS come on… |
|
I think this address the question: As mentioned, NativeAOT is just experimental and it has no clear roadmap and probably no future. What I can recommend is moving on, I can recommend using Vala+GTK+Glade (for xml UI), it is very similar to C#. It converts the code to C and compile, so you even have the benefit of cross-compile and no JIT. There's quite a good amount of software made with it. |
Uh oh!
There was an error while loading. Please reload this page.
Apparently the long term roadmap will be to merge Win32 and UWP worlds into a common development experience.
Given the newly introduced C#/WinRT and the ONE .NET effort announced at BUILD, where does it leave .NET Native in a Project Reunion world?
All reactions