visual studio 2013 - NuGet: what should go into TFS? -

I am working on a client project; They are hosting TFS server.

I started working on an existing body code, in particular a library which is a member of the solution and is bound to control the TFS version. (Small padlock icons appear on this project.) I added a unit test project to go with it. I believe that when I added the test project, I did not specify "Tie in Versions Control", and therefore manually added the project to TFS. It's all right.

I've added the NuGet package dependency for both library and unit testing. In both cases, the only change in TFS repo was a new packages.config file. When a customer's build server is built, it captures the package with NuGet. Customer is happy with this; Maybe they should not be?

Then I made another application project with my own solution, sharing some projects in the original solution. When I created a new project, I "forced the version control". I've added the same package dependencies, but this time there is a new package folder that contains package DLL, and everyone was added to TFS; There was no packages.config file.

I got a link that was told to me how to "enable package restore", and tried to do it; Now I have a .nuget directory in the solution; A repositories.config has been added to the package ; And in the changes in Share .csproj files, and , I still have package binary for checkin.

I think I will need to start with this new solution, but I want to do the right thing, it is not clear to me that using only one packages.config Managing packages is the right thing I have to discourage the use of package restoration.

I'm working with the Express Edition of VS 2013, if it does make any difference.

You have the nuget.config file, package.config file in the project, repositories.config with the package folder and Changes to the project file should check the .nuget directory.

You should not check binaries in the package folder, they will be downloaded from Nugget during build.