CODEWITHSUNDEEP
visual-studiotfsnuget
Andy
Andy

Reputation: 2749

Visual Studio + nuget + TFS: checking in nuget packages?

I'm working on a TFS project with a small team. This project has a bunch of nuget packages installed, but it's for a 4.0 project, and the nuget package manager GUI doesn't even offer the older versions of the packages any longer since their 4.5 equivalents are now being used. In order to allow other team members to compile the project, they need to have the exact versions of the packages. I'd like to check in the entire "packages" folder used by nuget. Is this a good idea? If so, how does one check in the "packages" folder and all its contents since it exists at the solution level? There is no "Include in Solution" option in Visual Studio as there is when you right-click an assembly.

Upvotes: 9

Views: 4508

Answers (2)

Paul Swetz
Paul Swetz

Reputation: 2254

We use an on-prem TFS install with no internet access so we have to check in our package folders or our builds fail. The biggest issue is that VS does not behave consistently when it comes to adding the pending changes for new package files, often times it will ignore the .dll files in the pending changes window, sometimes it adds everything fine.

Upvotes: 1

Horizon_Net
Horizon_Net

Reputation: 5979

in the past I have also checked in the NuGet packages into version control. With this some problems appeared:

  1. Some packages where not checked into version control when committing from Visual Studio into TFS.
  2. Updating packages became a real problem.

For the first problem I had used the TFS Power Tools. The problem with this solution is that every developer needed to install the Power Tools.

A better solution came up with NuGet 2.7. It introduced package restore. With package restore there's no need to check-in the packages folder. They will be restored during build.

Upvotes: 1

Related Questions