-
Notifications
You must be signed in to change notification settings - Fork 1.1k
[WIP] dotnet run: --from-source #48443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Commented offline that we wanted to start with "dotnet tool run --from-source". We're currently discussing alias options or auto-detection options but the full command is safest to start with. |
@edvilme I would recommend patterning this more off of local tools than global tools. Global tools download the packages to a folder structure under Local tools on the other hand run directly from the packages in the NuGet global packages folder. I think it would be easier to run a tool from there without any side effects besides the fact that the package is now in the global packages folder. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Things to consider for review when it is finished / good test cases:
- Does it delete the tool, as it says without permanently installing it
- It passes the args to tools
- Version resolution works
- Uses latest if no version specified
- It uses the feed
- Make sure we prompt before downloading something new
- Does it have -y -n
- Supports nuget feed options
I like dotnet toolx personally but ok to see why we are using --from-source for now since it matches the other patterns.
Closes #31103
WIP: Name, and implementation may change