Thanks for the comments but I must be being a bit thick or missing something simple. Assuming I want to commit packages to source control (Visual Sourcesafe at the moment in our case), i.e to quote "The current NuGet workflow has always been to commit the
Packages", then *how* do I do this in a way that is managable and that I can ensure I always have the latest versions when I download the solution from sourcecontrol?
To cause less friction for our developers, unless something has screwed up, all our source control management is done via Visual Studio. We get a sln file, we add files to the project and check-in through Visual Studio. Anything *not* at project level we
handle through solution files.
As far as I can tell, the packages.config will get added to the project file automatically (and hence into Sourcesafe on checkin) but the packages will not as, correctly IMO, they are held at solution level and not added to the project file. This means they
will not be added to sourcecontrol or maintained on a get latest etc. I have to leave my Visual Studio environment and add them manually through SourceSafe explorer.
I guess to get update or new packages added since the last time I did a "get latest" on the source code, I would have to use NuGet as I can't depend on Visual Studio as it doesn't know about the new/updated packages. I can't remember, but I presume NuGet
warns me that new packages are required??
I'm just trying to work out the expected workflow if you *do* want to commit packages to source control and how to make this as frictionless as possible. I didn't spot any resolution to the issue from dfowlers thread....