Thanks, jrummell, I studied that famous link quite a bit. Do you remember what kind of package you had that linked to Chutzpah? It seems Chutzpah only lives in the top level packages.config, and the VS package restore via CI (msbuild) doesn't restore that package. Visual Studio's package manager only lets me uninstall the package; no manage option. I believe this is why the solution build itself won't update it... because it doesn't find it in any project packages.config.
I am working around it by using a separate TeamCity build step (a Nuget Install runner) which DOES update chutzpah. This wastes build time because it's trying to update twice... once from the solution and then once in this step. I hope to continue to get support here and work through the issue so I can have it build with the solution itself.
And by VSS I didn't mean Visual Source Safe :). I mean source code control (generic). We are using SVN and moving to GIT in the next year.
I am working around it by using a separate TeamCity build step (a Nuget Install runner) which DOES update chutzpah. This wastes build time because it's trying to update twice... once from the solution and then once in this step. I hope to continue to get support here and work through the issue so I can have it build with the solution itself.
And by VSS I didn't mean Visual Source Safe :). I mean source code control (generic). We are using SVN and moving to GIT in the next year.