I'd like to find a way to have my nuget packages downloaded automatically if they are found to be out of date or non-existent in the solution. Preferably such a download would occur either at open or build of the solution.
My company has several different products with dependencies to dozens of 3rd party vendor components. We currently manage those dependencies by using relative path references in the projects and known sets of assemblies. Developers copy an "assembly"
folder from a standard location to the solution folder when they pull a new file set from source control. Everything then compiles against that copied reference set and they can continue working.
I'm hoping to use nuget in such a fashion that the configuration files will be saved to source control but the actual assemblies will not. Then when a new developer gets latest from source control the latest package config is pulled and on solution open/build
any missing or out of date assemblies would be copied to the packages directory.
I'm sure there must be ways to accomplish this but as a nuget newb (is that a nub?) I haven't figured it out yet.
Any suggestions you might have will be greatly appreciated.