NuGet feed hosting options including MyGet
myget, nuget, nuget-package, nuget-server, package
Solution
As one of the founders of MyGet let me take this question :-) We indeed have around 1.500 feeds hosted on our public website, we also have some enterprise users who have their own domains and are not listed here. Feel free to contact us if you require more info or want to be in touch with one of them. We're also open for just a chat so feel free.
In the Gallery (http://www.myget.org/gallery) we have famous projects like SignalR, RavenDB, Glimpse and the ASP.NET team is pushing their nightlies as well.
In the field, we see a lot of "self hosted" solutions based on NuGet.Server but these are typically smaller installations. Just as with network shares, it lacks a bit in performance when too many packages are in that feed.
Problem
I have been investigating options for NuGet feed hosts. Currently, we use TeamCity to build/publish packages to TC's built-in server. For a Visual Studio package-source pointed to TC, we've found that the subscription/update process to be painfully slow -- even though our developer workstations are within the same local subnet and we have only a few dozen packages. Other package-feed options I know about : - nw share - internal web-server(s) based on NuGet.Server - MyGet - ProGet Does anyone have enterprise-level experience with any of these solutions ? MyGet looks very promising, but one cause for concern is that ( at least according to their website ) only around 1500 feeds are active. If MyGet had truly caught on, it would seem that this should be 150,000 or so. Also: is there anything in the NuGet world similar to Maven's concept of a local-only "snapshot" package engine and feed server ? Thanks.