Replies: 1 comment 1 reply
-
Yes, exactly. Consider the scenario of an iterative development process on your local machine where you build the Dockerfile. Once the restore has been executed the first time and you've not changed the content of the csproj since, you don't need to bother executing the restore again when you're building your code changes. It will be cached. This is nice because restore can take a fair amount of time depending on how many NuGet packages are involved. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you, that makes sense. May be useful to add a note for that in the samples, for the less experienced folk like me :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This seems to be assumed:
Why do that, instead of directly building?
Is it purely to be able to cache the restore step?
Beta Was this translation helpful? Give feedback.
All reactions