Setting up a NuGet Server is so easy that everyone should do it. Why? If you are beholden to corporate policies that restrict the applications and references your projects can have, you can still benefit from the awesomeness of NuGet by hosting corporate approved packages. If you have a critical build process, you may not want to depend on the reliability of third party servers. Oh, I can keep going, but I won’t. The point is with 5 easy steps (depending on how you may break it down), you can have a NuGet server up and serving packages.
- Create an Empty Web Application (I’m using Visual Studio)
- Use NuGet to add reference in the Web Application to “NuGet.Server”
- Add the nupkg files that you want to host to the Packages folder
- Deploy the Web Application
- Add the URL of the Web Application to your local NuGet package manager.
Thanks to docs.nuget.org and Adam James Naylor for opening my eyes to how simple this is: