Hi Greg, Check out http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packagesfor details of how to get nuget to manage the dependencies without checking in all of those files into source control. This gets even more powerful if you have a corporate NuGet server so that you get to control all of the dependencies without duplicating them over and over in the repository.
Michael M. Minutillo Indiscriminate Information Sponge http://codermike.com On Wed, Jan 25, 2012 at 3:36 PM, Peter Gfader <pe...@gfader.com> wrote: > Hi Greg > > >>Then I see that it has created a packages folder under my solution > folder containing 55 files in 4 folders with a total size of 3.8MB. Now > this seems a bit heavy-handed ... it will create duplicated and redundant > files in projects everywhere, multiple tool versions can be installed, and > it will make version control and deployment trickier. > > Why would you say that it makes deployment trickier? > > I am not a big fan of having lots of duplicated files either, for every > little pet project. But the advantage is that it just works: Get latest > from source control -> all references can be resolved... > > .peter.gfader. > http://blog.gfader.com > > fat fingers + tiny touchscreen -> short emails > On Jan 25, 2012 7:53 AM, "Greg Keogh" <g...@mira.net> wrote: > >> People have been talking about NuGet a bit so I thought I’d try it out.** >> ** >> >> ** ** >> >> The very first thing that confused me was the relationship between the >> NuGet packages I install and those that I have already installed by other >> means. For example I get packages for Entity Framework, Nunit and SQL CE, >> but I already have these installed. So I opened a small console app and >> added the NUnit package to see what happens. I see that it adds 3 >> references like this sample:**** >> >> ** ** >> >> E:\dev\command\myapp\packages\NUnit.2.5.10.11092\lib\nunit.framework.dll* >> *** >> >> ** ** >> >> Then I see that it has created a packages folder under my solution folder >> containing 55 files in 4 folders with a total size of 3.8MB. Now this seems >> a bit heavy-handed ... it will create duplicated and redundant files in >> projects everywhere, multiple tool versions can be installed, and it will >> make version control and deployment trickier. I’m utterly bewildered by >> what NuGet has done and find it hard to believe that anyone would find this >> acceptable.**** >> >> ** ** >> >> Am I missing something?**** >> >> ** ** >> >> Greg**** >> >
