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.
Thank Bog I just bought 1000 shares of a well established supplier of candles in the UK! I'd invest in warm, fuzzy sheep, too, but I'm sure you already have your favorites - for warmth, of course. Wise choice, renewable and organic!
I'm thinking of setting up a private NuGet server for our development department.
TeamCity 2017.1 seems to have NuGet support, but the documentation is confusing, it gives the impression that this is only for self built NuGet packages which are stored with the build artifacts.
Anyone has got any experience with this, can I use it for standard NuGet packages ?
Where I work we use Teamcity for our own custom built libraries with Nuget packages.
It is possible although I am not on the team which configures the build server - so it is possible but not a very helpful answer... sorry
“That which can be asserted without evidence, can be dismissed without evidence.”
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.