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.
Is there an equivalent of DotNetCliToolReference that uses a solution-local project?
See original GitHub issueSteps to reproduce
I have a solution that has many projects in it, one of which is a tool that I’d like to use with DotNetCliToolReference . Using DotNetCliToolReference to reference a tool in the same solution doesn’t seem to be supported.
Expected behavior
In the same way that ProjectReference can be used instead of PackageReference, I would have hoped that there was an equivalent feature for a tool.
Actual behavior
I’m forced to build a package for the tool first, place it in a package repository (folder) and then reference the package.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:5 (3 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
@krwq The one issue I see with the local nuget method is that it’s hard to test new versions. For example, if I make one change to my tool code I have to increment the version or clear nuget cache every single time.
Let’s continue tracking this at NuGet/Home#2469