[nuget.exe] Restore does not no-op when packages already exist #1040

Closed
emgarten opened this Issue Jul 28, 2015 · 3 comments

Projects

None yet

3 participants

@emgarten
Contributor

Steps

  1. nuget.exe restore .\packages.config -packagesdirectory " \Visual Studio 2015\Projects\BugBash\BugBash\test" -Source https://www.nuget.org/api/v2/ -Source https://api.nuget.org/v3/index.json
  2. Run the above command again

Expected
The second run should say that all packages have been restored

Actual
Messages are logged saying that packages are being added

@deepakaravindr deepakaravindr self-assigned this Jul 29, 2015
@deepakaravindr
Member

@emgarten, Note that if the solution has an UWP project, it will always say that there are packages to be installed. However, if the solution only has legacy projects, and the packages are already installed, you will not see messages that packages are being restored. I have verified. Did you use a solution with UWP projects in them?

@emgarten
Contributor

@deepakaravindr it had a mix, however that should not cause packages.config projects to restore all packages when they already exist. The messages about adding packages should be skipped.

@deepakaravindr deepakaravindr added a commit to NuGetArchive/NuGet.PackageManagement that referenced this issue Jul 29, 2015
@deepakaravindr deepakaravindr Fixes NuGet/Home#1040 and
NuGet/Home#992

Force changing SolutionDirectory and PackagesDirectory to be full path
right before they are used. While reading settings, we need to pass the full
path and NuGetPackageManager needs a full path too
8d98c6f
@deepakaravindr deepakaravindr added this to the 3.1.0-commandline milestone Jul 29, 2015
@deepakaravindr deepakaravindr referenced this issue in NuGetArchive/NuGet.PackageManagement Jul 29, 2015
Merged

Package restore fixes v #49

@RanjiniM RanjiniM added the 2 - Working label Sep 1, 2015
@RanjiniM RanjiniM assigned emgarten and unassigned deepakaravindr Sep 1, 2015
@emgarten emgarten added 3 - Done and removed 2 - Working labels Sep 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment