You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And readers could choose the specific standard version, just like the old MSDN library does, switching between different .Net Framework versions. I guess cross-platform class library developers are tend to target "netstandard1.x", but the only API references availabe now is the .Net Core API docs. This might bring confusion and inconvenience.
The text was updated successfully, but these errors were encountered:
jarenduan
changed the title
It would be best that there is a .NET Platform Standard API references.
It would be best if there is a .NET Platform Standard API references.
Jul 16, 2016
I think it would be best to create an API reference using the API versions for the specific packages using the map here.
The .NET Standard version could then be mapped to that package's API version
(i.e. instead of using only netstandard1.3, use (package name)+(API version of package) and map that to netstandard1.x)
And readers could choose the specific standard version, just like the old MSDN library does, switching between different .Net Framework versions. I guess cross-platform class library developers are tend to target "netstandard1.x", but the only API references availabe now is the .Net Core API docs. This might bring confusion and inconvenience.
The text was updated successfully, but these errors were encountered: