Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Command returns empty list if tool is not found #40207

Closed
tdykstra opened this issue Mar 25, 2024 · 0 comments · Fixed by #40616
Closed

Command returns empty list if tool is not found #40207

tdykstra opened this issue Mar 25, 2024 · 0 comments · Fixed by #40616
Assignees
@tdykstra
Labels
doc-bug Problem with the content; needs to be fixed [org][type][category] dotnet-fundamentals/svc okr-quality Content-quality KR: Concerns article defects (bugs), freshness, or build warnings. 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer Indicates issues where the customer no longer needs any help. [org][resolution] user-feedback Issues related to "Unified User Feedback".

Comments

@tdykstra
Copy link
Contributor

tdykstra commented Mar 25, 2024 •
edited by sequestor bot
Loading

Type of issue

Other (describe below)

Description

Verbatim from the feedback control:

Under the header "Arguments" it shows for PACKAGE_ID "Provides a way to check if a specific tool was installed. The command returns 1 if no tool with the specified package ID is found; returns 0 otherwise."That is exactly what I need, but that's not what it does - it just returns an empty result. Meaning the "table headers" are written to the cmd window, but then no entries underneath it.

Page URL

https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-tool-list

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/tools/dotnet-tool-list.md

Document Version Independent Id

27f38a93-1b87-d5e2-c7d4-29faf36ea521

Article author

@tdykstra

Metadata

  • ID: 3ceadded-82f0-9b11-36b3-a5582a4a57d7
  • Service: dotnet-fundamentals

Associated WorkItem - 239903
@tdykstra tdykstra added the user-feedback Issues related to "Unified User Feedback". label Mar 25, 2024
@tdykstra tdykstra self-assigned this Mar 25, 2024
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Mar 25, 2024
@tdykstra tdykstra added doc-bug Problem with the content; needs to be fixed [org][type][category] and removed ⌚ Not Triaged Not triaged labels Mar 25, 2024
@dotnet-policy-service dotnet-policy-service bot added the okr-quality Content-quality KR: Concerns article defects (bugs), freshness, or build warnings. label Mar 25, 2024
@tdykstra tdykstra added 🗺️ reQUEST Triggers an issue to be imported into Quest. and removed Pri2 labels Apr 2, 2024
@sequestor sequestor bot added 📌 seQUESTered Identifies that an issue has been imported into Quest. and removed 🗺️ reQUEST Triggers an issue to be imported into Quest. labels Apr 2, 2024
@tdykstra tdykstra mentioned this issue Apr 24, 2024
Merged
@tdykstra tdykstra moved this from 🔖 Ready to 👀 In review in dotnet/AspNetCore.Docs April 2024 sprint Apr 24, 2024
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in dotnet/AspNetCore.Docs April 2024 sprint Apr 25, 2024
@dotnet-bot dotnet-bot added the resolved-by-customer Indicates issues where the customer no longer needs any help. [org][resolution] label Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tdykstra tdykstra

Labels
doc-bug Problem with the content; needs to be fixed [org][type][category] dotnet-fundamentals/svc okr-quality Content-quality KR: Concerns article defects (bugs), freshness, or build warnings. 📌 seQUESTered Identifies that an issue has been imported into Quest. resolved-by-customer Indicates issues where the customer no longer needs any help. [org][resolution] user-feedback Issues related to "Unified User Feedback".
Projects
No open projects
dotnet/AspNetCore.Docs April 2024 sprint
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

dotnet tool list always returns 0 dotnet/docs
2 participants
@tdykstra @dotnet-bot