MyGet is used within Dangl IT GmbH as a central source for all our deployed packages, thus allowing us to structure our software projects logically and reuse existing code where applicable.

So far, we haven't had any problems with MyGet, it works as expected. We would like to see the addition of upstream sources, since we've never been able to get this working, but this is a low priority for us at the moment.

Overall, I've solved some serious problems that stem from trying to get everybody to have the same version of packages - developers, QA, and clients get the right stuff, and that makes a lot of work just plain go away. The setup was not horrible and consultants are productive. I can't think of a better experience!

MyGet has revolutionized how I've done consulting. I used to use Git subrepos to bring code into projects, since I didn't want to put NuGet packages in a public place. Now that I have pioneered using MyGet, a company with whom I work is pulling together all of our Maven, NuGet, and npm packages. The administration and delivery for MyGet is awesome, and uploading packages is mostly pretty easy. For the money, this is a no-brainer for the organization: we can deliver packages to clients without everybody having access to source code. I love it.

It took me some time to figure out how to get the permissions set up. There is a way to get a pre-authorized URL, which I would prefer not to do. However, I've seen NuGet have some trouble authenticating from QA machines. I don't have an answer for that, but I feel authorization could be a little more clear. I would love to see a Docker registry! I went with MyGet over GitHub's package manager because we don't use GitHub for anything else, but it was a close call. I hear that MyGet is working on Docker registries. At that point, I believe MyGet will satisfy more than my needs...like all of my wants, too.

MyGet is one of the good 3 options for a package registry as a service in my humble opinion. That being said, I'd love to see more new features (or more communication) and better up-time.

MyGet has a very good interface for looking at your feeds. The API works. They just (March of this year 2020) added snupkgs support which is nice, but they're are a few competitors which have had this for a while. While this is true with most private package registries, the registration and authentication for your registry is very simple.

The biggest difficulty for us with MyGet is their up-time. We depend on MyGet for a majority of our builds so when MyGet is down, most of our builds are down. This hit us ESPECIALLY hard during a release where we had the majority of a day (in November 2019) where we couldn't build. We actually moved some of our packages to GitHub Packages for the day so we could continue for a bit. As of 2018, new features (or at least posts about new features) have died down a bit. They appear to be either slowing down in new development or just simple not communicating as much.

It has been easy to setup, consume, and maintain.

We needed as easy to setup and consume private nuget feed. We found that in MyGet.

Honestly, since all we were looking for was a private nuget feed that we didn't have to host, MyGet had everything that we wanted. I haven't encountered a gap in features.

Solid performant service.

MyGet lets us build and store our private npm packages, as well as keep a copy of every dependency we use so we are protected from another leftpad incident. We are also able to protect ourselves from an old dependency being taken over by a malicious maintainer.

It's hard to update dependencies of dependencies of dependencies. (3 levels deep). 2nd level dependencies are easily updated.