Checking in packages from NuGet into version control?

version-control msbuild nuget
Scott Weinstein picture Scott Weinstein · Feb 12, 2011 · Viewed 17.2k times · Source

Prior to NuGet, it was common accepted 'best practice' to check-in all external DLLs used on a project. Typically in a Libs or 3rdParty directory.

When working with NuGet, am I supposed to check-in the packages directory, or is there a way for MSBuild to auto download the needed packages from the nuget feed?

Answer

Edward Wilde picture Edward Wilde · Oct 1, 2011

No

Since this question was asked there is now an easy workflow to use NuGet without commiting packages to source control

From your package manager console you need to install the 'NuGetPowerTools':

Install-Package NuGetPowerTools

Then to enable your projects to support pack restore you need to run another command:

Enable-PackageRestore

Now you are ready to commit your code base without the packages folder. The previous command changed your project files so that if packages are missing they get automatically downloaded and added.

Source

Using NuGet without committing packages to source control

Related questions

MSBuild -- Use the .csproj file or roll your own?

OK, so I readily concede that I'm a newbie when it comes to continuous integration. That being said, I'm trying to set up a CC.NET environment to educate myself, but I'm having trouble finding the information I need to …

Read More
Subversion oddity - svn info revision higher than last changed rev on project folder

Got something going on I can't explain. I have a working copy of my project - done svn update (which says: Updated to revision 1895), I know it's the latest. When I perform an svn info on the project folder, the …

Read More
How do I undo the most recent local commits in Git?

I accidentally committed the wrong files to Git, but didn't push the commit to the server yet. How can I undo those commits from the local repository?

Read More