Solution Tools
- Dominant language
- C#
- Stars
- 3.2k
- Forks
- 1.3k
- PR merge metrics
- PR metrics pending
Description
### Is your feature request related to a problem?
I have a solution with several projects (as is quite common), one of which is essentially a command line tool that is used to keep another project up-to-date when its dependencies (OData services in this instance) have changed.
At the moment I have a batch file in the dependent project which just executes `dotnet run` on the command line project. The "dotnet tool" functionality seems like an obvious fit for this, but my tool is not generic so I cannot put it on NuGet and even installing it as a local tool requires the project to have been built and additional inputs to specify a local path or for it to be in a local package source.
### Describe the solution you'd like
What I would like is to be able to define the project for that command line tool as a 'dotnet tool' so that it can be invoked without the need to install anything or take any additional steps (ala dnx) so that other members of my team can just get the code and just start working with it, without needing work their way through manual installation steps.
### Alternatives you've considered
I'm currently using a batch file which runs `dotnet run --project ...` to execute the command line project from source, which works, but doesn't feel like quite the right solution.
Another option would be to make a local package source and add the tool to to that and use `dotnet tool restore` to make the tool available, but that still requires manual steps to be taken and feels disjointed when my tool is _in_ the solution I want to use it from.
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing `dotnet tool` and `dotnet run --project ...` workflows described in the issue, including local-tool restore and local package source requirements. Define and validate a solution-project workflow that invokes the in-solution command-line tool without manual installation or additional inputs, while preserving the team’s checkout-and-start experience.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100