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
I pre-installed some packages in the global nuget cache folder by using nuget install packages.config to reduce package download time when run restore command before build.
And it works, it hits local cache and just downloads missing packages.
But the dotnet restore command runtime is increasing.
After finding log, it always staggers in checking compatibility:
I want to know what causes this?
To Reproduce
Install thousands of packages and packages have different versions in nuget global cache folder.
Then run dotnet restore *.sln -v d can reproduce it.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I pre-installed some packages in the global nuget cache folder by using
nuget install packages.config
to reduce package download time when run restore command before build.And it works, it hits local cache and just downloads missing packages.
But the dotnet restore command runtime is increasing.
After finding log, it always staggers in checking compatibility:
I want to know what causes this?
To Reproduce
Install thousands of packages and packages have different versions in nuget global cache folder.
Then run
dotnet restore *.sln -v d
can reproduce it.Beta Was this translation helpful? Give feedback.
All reactions