Nuget, the defacto package managment system for .NET development, has come a long way in a relatively short time. It does a pretty good job at simplifying and automating the process of downloading and referencing 3rd party libraries. It takes most of the guess work out of which versions of which dependencies need to come along for the ride in order for everything to work. It even works from both inside and outside of Visual Studio.
Kudos to Microsoft stepping into the package management space and working with the community to create a tool that many of us have come to depend on.
Using Nuget within a large project is not without it’s risks, however, so I share the following recommendations in the hopes that it saves someone else some time and trouble.
- NuGet Tip #1: Restore Packages on Build
- NuGet Tip #2: Run your own package feed
- NGet Tip #3: Manage Packages at the Solution Level
I will update this list as the tips come out.