Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Local dotnet tool management #248

Open
badsyntax opened this issue Dec 18, 2022 · 0 comments
Open

Local dotnet tool management #248

badsyntax opened this issue Dec 18, 2022 · 0 comments
Labels
enhancement

Comments

@badsyntax
Copy link
Contributor

badsyntax commented Dec 18, 2022 •
edited
Loading

Is your feature request related to a problem? Please describe.

I'd like to be able to manage my local dotnet tool packages and versions (eg using dotnet-ef tool to run migrations etc)

Describe the solution you'd like

Similar to how packages are displayed, I'd like to see a list of my local dotnet tools with installed version, and allow me to delete/add/update them.

Tools can be discovered via dotnet tool list --local

This is how I imagine it'll look:

New top-level "Local Tools" tree:

Screenshot 2022-12-19 at 12 05 21
badsyntax added a commit to badsyntax/vscode-solution-explorer that referenced this issue Dec 19, 2022
@badsyntax
Add local dotnet tools management. Fixes fernandoescolar#248
e63937f
badsyntax added a commit to badsyntax/vscode-solution-explorer that referenced this issue Dec 19, 2022
@badsyntax
Add local dotnet tools management. Fixes fernandoescolar#248
18d8788
badsyntax added a commit to badsyntax/vscode-solution-explorer that referenced this issue Dec 19, 2022
@badsyntax
Add local dotnet tools management. Fixes fernandoescolar#248
3732cfe
@badsyntax badsyntax mentioned this issue Dec 19, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add local dotnet tools management badsyntax/vscode-solution-explorer
1 participant
@badsyntax