I figured it out eventually. I had checked in the packages folder, no dlls. Because I had done that, using the Nuget package restore thought it already had all of the packages. Removed the packages folder entirely from source control (and deleted local copy) and then the Nuget package restore kicked in when i did a build. Then you just check in the Nuget folder that is added to the solution when you enable package restore. (ignoring the package folder which is managed by nuget locally).
works as advertised when you RTFM. :) thanks for the reply though. If I hadn't asked the question I wouldn't have figured it out for myself. lol cheers, Stephen On Wed, Sep 26, 2012 at 2:51 AM, David Kean <[email protected]>wrote: > You checked in the packages folder without the dlls? The dlls are under > the packages folder. If you don’t want to check in the dlls you can do > what’s called package restore, which pulls down the packages dynamically, > however, a change in the later version means that each developer box needs > to opt into this, so it’s a lot easier to check the entire packages folder. > When you update packages, NuGet automatically removes older versions if no > one is using them.**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Stephen Price > *Sent:* Tuesday, September 25, 2012 6:12 AM > *To:* ozDotNet > *Subject:* NuGet question**** > > ** ** > > Hey all,**** > > ** ** > > Just started playing about with NuGet, and checked in the packages folder > into TFS. Did a get latest on my other machine and thought that NuGet would > toddle off and get the latest dll's that it was missing (Didn't check in > the dlls).**** > > Have I misunderstood something about what it does? Or am I trying to make > it do something it ought not?**** > > ** ** > > Is there a trick to make NuGet work with source control?**** > > ** ** > > cheers,**** > > Stephen**** >
