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.
Using a tool package from a local feed doesn't work
See original GitHub issueI’m building a .NET Core cli tool and I want to test it before uploading a package. Now unfortunately tools can’t be referenced from projects in the same solution (as was the case with dnx commands), so I built a package and I’m using a local feed to serve it.
The following is the error I get:
No executable found matching command "dotnet-[the path to the project that I'm testing the tool with]"
The expected command name should have been dotnet-[toolname] but the cli is looking for the name above instead. Everything works great if I use a previous version that I already uploaded to nuget.
So what is the best way to test tools locally?
Environment data
.NET Command Line Tools (1.0.0-preview1-002702)
Product Information: Version: 1.0.0-preview1-002702 Commit Sha: 6cde21225e
Runtime Environment: OS Name: Windows OS Version: 10.0.10586 OS Platform: Windows RID: win10-x64
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
This other issue in cli project says the same (still by @brthor, thanks): https://github.com/dotnet/cli/issues/3239#issuecomment-243959757
Ah sorry, the above reference is for another issue, I got them mixed up. Your link though is good, it appears there are discussions about it so we can hope.