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.

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

Commands to be reviewed for the future #5202

Closed
5 tasks done
blackdwarf opened this issue Feb 25, 2016 · 3 comments
Closed
5 tasks done

Commands to be reviewed for the future #5202

blackdwarf opened this issue Feb 25, 2016 · 3 comments
Assignees
Milestone

Comments

@blackdwarf
Copy link

This issue lists the overall commands that need review and design on how they work.

Commands

Intra-command interaction

@blackdwarf blackdwarf self-assigned this Feb 25, 2016
@benrr101
Copy link

What's the status on these commands? I see dotnet-install-package and dotnet-commands have checks beside them, but neither of them appear to be in the latest build (preview3-003592)

@gulshan
Copy link

gulshan commented Jan 6, 2017

If dotnet install can be restricted to donet cli tools only, it be very useful IMHO. There can be a separate command for normal nuget packages.

@livarcocc
Copy link
Contributor

All the other tracking issues have been closed. Closing this one as well. We are working on dotnet install tools for the .NET Core 2.1 release.

wli3 referenced this issue in wli3/cli Nov 14, 2018
* Adding the OptIn test matrix for NuGet references - dotnet/sdk#1066

* Resolving: dotnet/sdk#1327

* Put the constructor back...

* Backing out change for dotnet/sdk#1327 due to Jenkins failures
@msftgits msftgits transferred this issue from dotnet/cli Jan 31, 2020
@msftgits msftgits added this to the Backlog milestone Jan 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants