NuGet and Distributed Version Control (DVCS)

Question

I wonder if nuget can only be used to store links to required packages in version control (only the .config package and ignore the package folder).

Is there a way to tell nuget (re) to load all the referenced packages into the various package.config files? Or something similar that could be added to the assembly script.

Update:

I don't seem to be the only one who requested this feature: See this work item (thanks to PHeiberg for the tip)

Update 2:

NuGet now has this feature. See Using NuGet Without Transferring Packages To Source For more information . All the rest is to add the package directory to .gitignore or some equivalent of your VCS ( /packages/ will do the trick if you have it in the root directory of your repository and use git).

Answer 1

I just found out about NuGetPowerTools: https://github.com/davidfowl/NuGetPowerTools

Also see: http://blog.davidebbo.com/2011/08/easy-way-to-set-up-nuget-to-restore.html

Update: NuGet 1.6 now supports package recovery: http://docs.nuget.org/docs/release-notes/nuget-1.6

Answer 2

I do not know about your first question.

As for the fact that the CI server automatically updates packages, this can be done theoretically. You can link the List-Package-Installed and Update-Package commands and update each package to the latest version. For more details see the Link for reference .

Scott Guthrie talks about this on the subject:

“You can integrate the command line using a CI solution and run the update-package explicitly as part of the / CI build process to pull it down. Honestly, I'm not sure what makes sense for the scripts we say, although, as usual, you want which Either the developer decided before upgrading the base runtime environment to depend on the new version. NuPack's default model would have the developer use NuPack to install the library - and NuPack will automatically check the package and source dependencies for control. Thus, another dev (or CI server ) you don’t need to use NuPack again - they can just synchronize their sources and assemblies. But, as I mentioned earlier - if you want to explicitly make an update as part of your CI you can. "

Edit:

After your comment, I see what you are trying to achieve. I found this long thread on the NuPack discussion list on this issue. The solution, apparently, will not be part of v1. The custom build task in CI of your choice and configuring your repo for him is the only solution I see. Please report the results. I was interested.

Answer 3

There is ongoing discussion on this issue on Phil Haack's blog , where he asks for feedback on how to resolve this issue.