Support for dotnet search command (equivalent to nuget.exe list, later search)

[livarcocc]

From @Kemyke on October 19, 2017 13:29

Steps to reproduce

There is no substituting functionality for 'nuget.exe list' feature. That would be great if it would be possible to use the dotnet CLI for automation on every platform. Currently the mono should be installed on Ubutnu to run nuget.exe. Is there a plan to add all the missing functionality to the dotnet CLI?

Expected behavior

dotnet nuget list

Actual behavior

There is no funcionality in the dotnet CLI to list the available packages.

Copied from original issue: dotnet/cli#7869

[rrelyea]

in talks with CLI team for proper design for dotnet.exe (may be dotnet search packages ...)

[divinebovine]

@rrelyea any chance that this will get looked at in next quarter or so? Adding this capability would help with some of our automation pipelines.

[rrelyea]

Shipped this in dotnet sdk 2.2.100.

[John0King]

@rrelyea I think the current dotnet list is not the proposal of this issue.
this issue is about search nuget package in nuget.org , and the current command dotent list is about list the reference of current project.
Should this issue be reopen ?

[nkolev92]

Related issue: #8040

[anangaur]

dotnet tool search command already works now with .NET 5. Obviously it applies a filter to search results. So can't we use that code to remove filter and support dotnet packager search? Its odd that too search is available but not regular NuGet package search :)

[John0King]

today, on Devbog https://devblogs.microsoft.com/nuget/getting-started-with-nuget-5-8/ , it saids that now nuget.exe support nuget search , but no dotnet nuget search

[John0King]

nobody care ?

[JonDouglas]

We do care. We do not have a formal spec for dotnet package search or dotnet nuget search, but when we do, you can check out our proposals in our repository & we'll notify all those in related issues.

[John0King]

this is really nobody cared！！！！！！
nuget.exe search https://docs.microsoft.com/zh-cn/nuget/reference/cli-reference/cli-ref-search
have been implemented a year ago, and dotnet cli still don't have this command.

related:
dotnet/sdk#9675 >> dotnet sdk repo issue
#7217 >> moved to nuget
#6060 >> referenced by #7217

it's a total year I mean.

[red8888]

Just want to add the community tool dotnet-search is frequently referenced as a workaround, but it doesn't support specifying sources and doesn't read the system config for auth so its not usable- the repo is also 3 years old.

https://github.com/billpratt/dotnet-search

[hiredgunhouse]

Wow, in just over 4 months it will be 5 YEARS!!! since this issue has been created.
How long does it take Microsoft to implement such an obvious feature that should have been there from the start?
I am speechless :)
BTW. This death by 1000 cuts all over the place makes me seriously consider ditching .NET for Java or Node.js.
C# is pretty great language but the platform and developer experience is far from optimal and we developers need both.

[pflannery]

This would be a great feature. It would remove some complexity from the versionlens vscode extension and would enable authentication without trying to fetch usernames and passwords for multiple sources on a "no need to know basis"

[JauniusPinelis]

This is really needed for better .NET development experience in VSCode. Hope this will be completed soon.

[boggylp]

Any plans on prioritising this? It's been an open issue for ~ 6 years now

[JonDouglas]

Folks...this is almost live! 🤩🚢