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
Visual Studio Package Management UI, Visual Studio Package Manager Console
Product Version
all
Worked before?
No response
Impact
No response
Repro Steps & Context
Before PackageReference, when packages.config was the only way to use Nuget, the global packages folder was very similar to a cache (except that nothing ever expired, or got cleaned automatically).
However, since the PackageReference feature came out, the global packages folder is where MSBuild, the compiler, and other build tools will read files from. Therefore, it is no longer private storage for NuGet's internal use. As a consequence, the NuGet team has progressively reduced calling the global packages folder a cache, even if many customers still call it the "NuGet cache".
The NuGet general options page in VS options, there's a button that still says "Clear Nuget Cache(s)". This could be renamed to make it more obvious that clicking the button deletes not only the global packages folder, but other ones as well. Also, it might help slowly de-associate the global packages folder as being "the cache".
Verbose Logs
No response
The text was updated successfully, but these errors were encountered:
NuGet Product Used
Visual Studio Package Management UI, Visual Studio Package Manager Console
Product Version
all
Worked before?
No response
Impact
No response
Repro Steps & Context
Before
PackageReference
, whenpackages.config
was the only way to use Nuget, the global packages folder was very similar to a cache (except that nothing ever expired, or got cleaned automatically).However, since the
PackageReference
feature came out, the global packages folder is where MSBuild, the compiler, and other build tools will read files from. Therefore, it is no longer private storage for NuGet's internal use. As a consequence, the NuGet team has progressively reduced calling the global packages folder a cache, even if many customers still call it the "NuGet cache".The NuGet general options page in VS options, there's a button that still says "Clear Nuget Cache(s)". This could be renamed to make it more obvious that clicking the button deletes not only the global packages folder, but other ones as well. Also, it might help slowly de-associate the global packages folder as being "the cache".
Verbose Logs
No response
The text was updated successfully, but these errors were encountered: