The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
On nuget there is a package Nuget.Server (or something like that). It allows you to create your own private Nuget feed very easily.
There is a little bit of documentation on how to use it.
After hosting it, you can use it in the same way as official nuget feed.
You can also automate publishing by adding scripts for that to your CI.
Of course you can also use paid services like MyGet or something.
I've been using ProGet for just over a year and I would absolutely recommend. It took away all of the (many, many) headaches we suffered under NuGet.Server.
- Installation/upgrade is a breeze with the installation wizard. Automatically installs/configures SQL server and all dependencies
- Option to run on its own integrated webserver instead of IIS
- Support for many types of packages in addition to NuGet - we've had great success using the extensible UPack format for client application deployment
- Simplified support for NuGet symbols - just push the *.symbols.nupkg to ProGet and it sorts everything out. No need to push the regular nupkg file to one place and the symbols file to another place.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.