Why Should I Use MyGet?

There are quite a few usage scenarios out there where MyGet fits in very well.

  • A feed containing only the packages you or your company often use
  • A feed containing only your (open-source?) project and its dependencies
  • A feed containing just a few packages that you want to use for a certain project: tell your developers to just install them all
  • A feed creating and pushing packages on itself by watching your GitHub/Codeplex/Bitbucket repository and triggering our Build Services

MyGet also plays nice and provides integration with the tools listed in the MyGet cloud below. If you're interested in migrating to MyGet, then take a look at our how-to migrate to MyGet page.

The MyGet Cloud

Tough one! If you look at MyGet for the first minute, you would think it's an identical solution to NuGet.Server, Orchard Gallery or NuGet Gallery. If you create an account, you will notice some differences though:

  • MyGet can set up a feed for you in less than 5 seconds
  • You don't have to set up or maintain your own infrastructure
  • There's support for multiple feeds per account in MyGet. NuGet.Server, Orchard Gallery and NuGet Gallery only support one
  • MyGet allows you to delegate privileges to other users without sharing an API key: everyone has their own, secure access to a MyGet feed
  • Multiple API keys per user: why give the build server your API key if you can give it its own?
  • And much more! Check the MyGet features for a complete overview.
Found an issue with the documentation on this page? We accept contributions!
Read our contribution guidance or edit this page's source on GitHub.