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
This experience looses all context of the users navigation history, and is unlikely to be the desired page for most people. I would expect the better locations would be
I realise that the history of nuget versions is static, but doco is a changing structure. but you could manage the redirects dynamically with all nuget pointing to a redirector https://docs.microsoft.com/nugets?Microsoft.EntityFrameworkCore.SqlServer&version=1.2.3
another option would be ad to nuget the ability to store more urls. eg "project hosting url", "docs url" etc
The text was updated successfully, but these errors were encountered:
Often searches will resolve to a nuget package. or people will know the nuget they are using and want to find the doco for it.
However most MS nuget
At the moment nugets point to generic getting stated pages. For example
All point to https://www.asp.net/
This experience looses all context of the users navigation history, and is unlikely to be the desired page for most people. I would expect the better locations would be
I realise that the history of nuget versions is static, but doco is a changing structure. but you could manage the redirects dynamically with all nuget pointing to a redirector
https://docs.microsoft.com/nugets?Microsoft.EntityFrameworkCore.SqlServer&version=1.2.3
another option would be ad to nuget the ability to store more urls. eg "project hosting url", "docs url" etc
The text was updated successfully, but these errors were encountered: