This repository was archived by the owner on Oct 4, 2021. It is now read-only.
[NuGet] Support no-op restores on opening a solution#4778
Merged
Conversation
On opening a solution containing projects that use PackageReferences
the restore that runs was forcing a restore for each project. This
resulted in the project.assets.json file being re-generated and
the projects being re-evaluated. Now if the package references have
not changed a no-op restore will occur. This makes the restore much
faster on opening a solution. It also prevents NuGet going online to
fetch NuGet package information if a wildcard is used for a
PackageReference or if the version cannot be found. In the Package
Console when a no-op restore occurs you will see the following
messages:
Assets file has not changed. Skipping assets file writing.
No-Op restore. The cache will not be updated.
Fixes VSTS #614192 - NuGet Restore is never a no-op
Therzok
approved these changes
May 11, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
On opening a solution containing projects that use PackageReferences
the restore that runs was forcing a restore for each project. This
resulted in the project.assets.json file being re-generated and
the projects being re-evaluated. Now if the package references have
not changed a no-op restore will occur. This makes the restore much
faster on opening a solution. It also prevents NuGet going online to
fetch NuGet package information if a wildcard is used for a
PackageReference or if the version cannot be found. In the Package
Console when a no-op restore occurs you will see the following
messages:
Fixes VSTS #614192 - NuGet Restore is never a no-op