-
Notifications
You must be signed in to change notification settings - Fork 320
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: What place has .NET Native after Project Reunion #53
Comments
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 |
Does #105 address this question? |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
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?
The text was updated successfully, but these errors were encountered: