Skip to content

Instantly share code, notes, and snippets.

@yishaigalatzer
Created May 14, 2016 02:20
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save yishaigalatzer/3eddfd1367502ea3794dc3289d499af4 to your computer and use it in GitHub Desktop.
Save yishaigalatzer/3eddfd1367502ea3794dc3289d499af4 to your computer and use it in GitHub Desktop.
Speed up restore on kudu and vs
### Goal
We want both nuget the CLI and msbuild based projects to be able to share a common set of packages on a machine.
The current global packages folder is per user and has to be populated once per machine. In azure deployment scenarios that will happen potentially on every deployment. Furthermore this data is on a persistent shared drive that is networked accessed making it much slower than a local drive in the dev scenario.
We want to speed up the initial restore and bring it to be comparable to existing desktop .net deployments.
### How
The suggestion is to configure a machine level expanded packages folder.
Nuget will restore packages only if they don't exist in the machine folder.
CLI and msbuild task will pick up binaries from both folders.
### priority
Packages in the user folder override the global folder.
### configuration
Nuget.config based will define the extra folder at the machine level, similar to how we define the global packages feed
The setting can be overridden by the user nuget.config
Reading the setting will be done by a nuget configuration library.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment