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.
Allow project references to be used as tools
See original GitHub issueCurrently tools only work as package references. If I try to use a project reference as a tool, I get a “not found” error.
It would be interesting to have the option of using project references as tools in cases where there’s a tool specific to a single project’s build. Having to publish a separate package for the tool is cumbersome.
An example is Kestrel, which has two projects under tools\ (GeneratedCode and LibuvCopier) that are used during the build:
https://github.com/aspnet/KestrelHttpServer/tree/dev/tools
I’d like to be able to rename those to e.g. dotnet-kestrel-codegen and dotnet-kestrel-libuvcopy and use them as tools in src/Microsoft.AspNet.Server.Kestrel/project.json.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:3
- Comments:8 (5 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
I would also like to see this, it makes developing tools easier for one thing but it’s also nice and symmetrical, it makes the system easier to understand.
i’d fine with having this post rtm though.
Tracking this in NuGet/Home#2469