When you pull down the samples I’ve linked, the packages folder is not included (mostly because it is huge).
To restore, the packages folder in Visual Studio 2010, right-click on the Solution and Enable the Package Restore option. This is really useful for both these downloads, and if you are building your solutions on a CI server so that you don’t need to check the packages folder into Git (saving space on your source code repository as well).
How is this a good thing? Checkout now becomes a two step procedure. Missing one step means the code is unusable. If connection to the mothership overlord NuGet server is severred, you’re basically f***ed unless you had catered for it previously. Everything needed to build the project is no longer in a singular location under source control. Every developer needs a specific tool to work. And all because we hate an initial checkout of a few megs of binaries? Really?
If you use TeamCity you also need to edit the csprojs in question (look for SolutionDir). NuGet 1.6 has a bug that forces msbuild to cd out of the sln directory and then back into the directory where the sln is located. If the sln is the repo root this will fail because TeamCity by default does the checkout to a random directory.
Works like a charm but be sure to have the latest nuget version installed: http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c