Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`dotnet tool install`s unlisted and depreciated version
See original GitHub issueDescribe the bug
Installing without a specified version doesn’t get me the latest listed version. I would expect to get 4.1.0, which I get when browsing NuGet, or doing dotnet tool search dafny, but I get 4.1.0.50509 instead.
To Reproduce
dotnet tool install --tool-path . dafny
Issue Analytics
- State:
- Created 4 months ago
- Reactions:1
- Comments:6 (4 by maintainers)
Top Results From Across the Web
dotnet tool install attempts to install an unlisted package on ...
Name a tool that clashes with an unlisted package that has a higher version than yours on NuGet. Further technical details. dotnet --info...
Read more >dotnet tool install command - .NET CLI
The dotnet tool install command installs the specified .NET tool on your machine.
Read more >NuGet API for unlisted / deprecated package
example: https://api.nuget.org/v3/registration5-gz-semver2/dotnet-tool-outdated/index.json · Share. Share a link to this answer. Copy link
Read more >release-notes
NET 6.0 tool; Auto-Restore after paket install an paket update ... DEPRECATED: /package-versions API was deprecated for lookup from NuGet team ...
Read more >dotnet-tool-run 0.1.1
A simple .NET tool to execute other dotnet tools without installing them globally or in a project.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yes, good call.
@baronfel, perhaps you mean https://github.com/dotnet/sdk/issues/32092, where the “DepMan” tool had version 0.0.4 in a private feed and unlisted version 1.0.0 at nuget.org, and .NET SDK chose to install 1.0.0.