Help us make content visible
We don't have a document that clarifies what .NET 5 is and what is in it. This information is scattered in a couple of blog posts but there's no coherent article about it.
Describe the new article
What is .NET 5?
I would like to see a section about mobile app development with .NET 5 too.
I think it's time to discriminate packages in nuget between Legacy Framework and .NET.
I think it's time to discriminate packages in nuget between Legacy Framework and .NET.
That's been part of nuget since the beginning, it's called a target framework. Now nuget could do a better job about allowing filtering based on that compatibility.
@welly87 the intent of this issue was to give feedback on the above doc proposal for .NET 5 (which is almost finished), not to discuss features or ask general questions about .NET as a whole.
https://github.com/dotnet/runtime/discussions - Discussions
https://github.com/dotnet/runtime/issues - Issues/Suggestions etc
Various features described in those blog posts about .Net 5 have been dropped or pushed off (java interop? ,aot?). This should be clarified along with the future pipeline for these features.
I would like to know how multi-platform development will be handled. I understand there will be a compatibility matrix with this overview, but will that matrix be implemented in nuget? Meaning if I mark a project as targeting linux and windows, will I still be able to install platform specific nuget packages.
Spell out the support policy and the implications of not being LTS
e.g. if you adopt .NET 5 you have to plan to do the work to move to 5.1 by date X and then upgrade to 6 by date Y
This is quite a change for who is coming from framework so I think it needs to be highlighted to avoid surprises
Does .net 5 = still follow the architectural layout of framework/standard/core e.g. would you mentioned .net core when speaking in the context of .net 5 and is C# 8 the go to language.
Most helpful comment
Spell out the support policy and the implications of not being LTS
e.g. if you adopt .NET 5 you have to plan to do the work to move to 5.1 by date X and then upgrade to 6 by date Y
This is quite a change for who is coming from framework so I think it needs to be highlighted to avoid surprises