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)
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.