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

dotnet restore is now an implicit command #23

Open
richlander opened this issue Jul 19, 2017 · 1 comment
Open

dotnet restore is now an implicit command #23

richlander opened this issue Jul 19, 2017 · 1 comment
Labels
Enhancement .NET Core 2.0

Comments

@richlander
Copy link
Member

dotnet restore is now an implicit command

With the release of .NET Core SDK 2.0, the dotnet restore command is now implicit for commands that require a restore to occur. In most cases, you no longer need to use dotnet restore. Build systems or other forms of automation may still want to call dotnet restore explicitly to control the time in which the restore occurs and potential uses of the network.

The following commands implicitly call restore:

  • new
  • run
  • build
  • publish
  • pack
  • test

You can pass --no-restore to any of these commands to disable implicit restore.

Details

Impact

The .NET Core development experience no longer requires explicit use of the dotnet restore command. This improvement is delivered with the .NET Core 2.0 SDK and works independent of the target framework.
@dotnet dotnet locked and limited conversation to collaborators Jul 19, 2017
@terrajobst
Copy link
Member

Reopening according to process.

@terrajobst terrajobst reopened this Nov 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Enhancement .NET Core 2.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@richlander @terrajobst