You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
nuget.exe install disables caching when no version is provided.
In 2.x this changed the install by removing the machine cache from the sources list (by default the cache is a source for nuget.exe packages.config scenarios). The hash would be verified but downloading the package again would be skipped.
In 3.x/4.x the cache is completely ignored and the package is re-downloaded each time using DirectDownload.
The install command code is the same between 2.x and 3.x/4.x, but behind the scenes caching has changed in 3.x/4.x.
This behavior seems like a very poor user experience, it should be possible to run install and still use the normal cache.
* Allow updating packages when -ExcludeVersion is used
* Improved detection of already installed packages when -ExcludeVersion is used
* Adding -Framework switch to allow setting the target framework used when resolving dependencies.
* Remove NU1000 code from packages.config restore errors.
* Avoid unneeded downloads when a version is not given and the package is cached.
* Disable parallel for mono
* Display errors and return a non-zero exit when install on packages.config fails
* Remove old files during upgrades with -ExcludeVersion
FixesNuGet/Home#5743FixesNuGet/Home#5737FixesNuGet/Home#5736FixesNuGet/Home#5741FixesNuGet/Home#5017FixesNuGet/Home#3957FixesNuGet/Home#2405
* Allow updating packages when -ExcludeVersion is used
* Improved detection of already installed packages when -ExcludeVersion is used
* Adding -Framework switch to allow setting the target framework used when resolving dependencies.
* Remove NU1000 code from packages.config restore errors.
* Avoid unneeded downloads when a version is not given and the package is cached.
* Disable parallel for mono
* Display errors and return a non-zero exit when install on packages.config fails
* Remove old files during upgrades with -ExcludeVersion
FixesNuGet/Home#5743FixesNuGet/Home#5737FixesNuGet/Home#5736FixesNuGet/Home#5741FixesNuGet/Home#5017FixesNuGet/Home#3957FixesNuGet/Home#2405
nuget.exe install disables caching when no version is provided.
In 2.x this changed the install by removing the machine cache from the sources list (by default the cache is a source for nuget.exe packages.config scenarios). The hash would be verified but downloading the package again would be skipped.
In 3.x/4.x the cache is completely ignored and the package is re-downloaded each time using DirectDownload.
The install command code is the same between 2.x and 3.x/4.x, but behind the scenes caching has changed in 3.x/4.x.
This behavior seems like a very poor user experience, it should be possible to run install and still use the normal cache.
https://github.com/NuGet/NuGet.Client/blob/6f8d529312187fa1b6734da8d4ed9dc3442b916c/src/NuGet.Clients/NuGet.CommandLine/Commands/InstallCommand.cs#L247-L249
The text was updated successfully, but these errors were encountered: