Honestly, for tool that’s supposed to make life easier and more robust I find myself battling with it often.
I’ve been upgrading some of the packages in one of my projects and ran into this pretty error:
The schema version of 'Microsoft.Bcl' is incompatible with version 2.1.31002.9028 of NuGet. The schema version of 'Microsoft.Bcl.Build' is incompatible with version 2.1.31002.9028 of NuGet. The schema version of 'Microsoft.Net.Http' is incompatible with version 2.1.31002.9028 of NuGet. etc ...
OK, so initially I thought I’ll update the version of Nuget that TeamCity is running. Updated that, reran the build … same problem. Odd I thought … did some Googling around and found out that you have the MANUALLY … yes you read that right MANUALLY update Nuget … What the very fuck? This tool gets worse in my opinion the more I learn about it.
SO, go to you .nuget directory in your solution and run this:
nuget.exe update -self
So just what the hell is happening when VS tells me Nuget Package Manager needs an update? … yet my nuget.exes in the solution where still launguishing around at version 2.1 … honest, this is shit!
Now I’ve gotten my Debug build to work, but I keep getting these errors on my release build:
The build restored NuGet packages. Build the project again to include these packages in the build.
This is EXACTLY what Nuget is supposed to bloody do! That is one of it’s core functions … run the build again? Can you tell that I’m seriously pissed off with this tool right now?