The build cache is awesome, I've chosen to just store the NuGet Cache and not the package folder directly, as that way the build is "cleaner". Here is my appveyor.yml:

# Retain the NuGet package cache between builds.
cache:
  - C:\Users\appveyor\AppData\Local\NuGet\Cache

We have another project that's a mixture of .NET and AngulaJS and we're using node NPM and bower as well as NuGet, I've went for the following config

cache:
  - node_modules
  - C:\Users\appveyor\AppData\Local\NuGet\Cache
  - C:\Users\appveyor\AppData\Roaming\npm-cache
  - C:\Users\appveyor\AppData\Roaming\bower\cache\packages

I chosen to keep the node modules as installing the node packages takes the majority the build time, (I think because it's building a lot of the packages like phantomjs) But it's not restoring the folder node_modules even though that's the example given in the (documentation)(http://www.appveyor.com/docs/build-cache).

Am I doing something wrong?

Ignore that last comment, I need to put the relative path to the node_modules as it's not off the root of the repository.

But now I'm receiving the following error after the build

The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

I suspect it's caused by the deep nesting of node packages. Other than moving the site to the root of the repository, do you know if this can be resolved?

It's just the node packages of the AngularSeed project. I've created a build from my fork, but it's not failing presumably because the project is in he root of the repo.

If you take the same packages and build it from a deeper folder structure I believe it will fail.

Hi Feodor

Thanks for the quick turn around.

I've tried and I'm no longer receiving the path too long error, but I'm receiving a failure with bower.

In my angular-seed fork, you can see the package restore worked fine when the site was in the rot of the repo, see successful build 0.1.6 using the build cache.

I then moved the site to a deeper folder. The initial build 0.1.8 went through fine as the node packaged were rebuilt due to not having been cached.

I then kicked off another build 0.1.9 where the node packages were restored from the build cache, but the build failed because I don't think the packages were correctly restored, resulting in the error with bower.

Are you able to look at the project to investigate, it's all open source, so you can fork my fork and run it for yourself on the DeepFolders branch..

Hi Feodor

I'm afraid it didn't work. The first build 0.1.10 worked as there was no cache to restore (did you delete it?) at the end the node_modules appear to be saved fine.

I then kicked off another build 0.1.11 but this time the build failed evan earlier at the point where it was restoring the node_modules.

Hope this helps with your investigations.

Hi Feodor

I'd getting late here in the UK and I'll soon be shutting down for the night, if you want to continue using my build, give me your email address and I'll add you to the Team, I'm following @appveyor so you can DM me @JamesSkimming you don't want to post it here.

Did you manage to get any further on this? Caching the various package caches has mostly mitigated any build issues.

I suspect this one could be a bit of a pain to solve and is inherent in the 255 character file path limit Windows sometimes has. Therefore in the interest of pragmatism, we can live with the occasional failed builds especially if you can provide the rebuild button.

Sorry didn't mean to confuse. The node package restore where the project root is deep but using the build cache to cache the node_modules folder is 100% reproducible. We're now running without that setting.

I initially raised this because of NuGet, Bower and npm restore issues. Adding the local package caches to the build cache has mostly mitigated the issue, but npm install still occasionally fails.

Basically, if fixing this too much effort, we'd be happy to live with the occasional build failures if we had a rebuild button.