-
Notifications
You must be signed in to change notification settings - Fork 643
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
.NET 2.1 - Add flag or indicator for global tool searching / discoverability #5762
Comments
Related? #5684 |
@spboyer , what tool will users use to search for Global Tools packages? Are you suggesting a command for dotnet.exe or NuGet.org filtering? |
Should be supported at the nuget API level. At which point the dotnet CLI and nuget.org site could implement the proper UI properties. |
And we are looking forward to doing that, along with author and stats I hope. :) |
I will add this to our backlog. We should meet and discuss requirements and timeline 😄 |
This is supported on the V3 search and autocomplete API, will be added in .NET 5 SDK with I think this is safe to close. Please let me know if you had another idea @spboyer. |
In .NET Core 2.1, Global Tools is now a thing allowing for installing tools using the
-g
flag similar to to npm, however discoverability is already becoming an issue even in Preview. Other than the list @natemcmaster has here -> https://github.com/natemcmaster/dotnet-tools, hard to find a good list and I am sure that there are more.Consider adding a tool flag/option to the search. There is a metadata item to search on or index on
<packageType name="DotnetTool" />
.cc:/ @natemcmaster @shanselman @KathleenDollard
The text was updated successfully, but these errors were encountered: