I wanted to exchange some experience regarding private NuGet feed hosting solutions.

We have used MyGet for years both for our private and public packages. But recently it became so unstable that it would not be responsible to not investigate the alternatives. I looked into Azure Artifacts first because, we already have Azure Devops and it comes free. The transition was mostly painless (I plan to write about it in more detail soon). But hosting public feeds doesn’t seem as easy. One needs to create a public project just for that. So, we still use MyGet for public feeds for now. But will move them also elsewhere.

What are your experiences with private feed hosting? Do you host them yourselves or use a paid service?

  • canpolat@programming.devOP
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Have you tried Github packages yet?

    No. Thank you for the suggestion. We use Azure Devops, but I would expect it to have good integration with GitHub. But creating a public project in Azure Devops may make more sense (so that all packages are in one place).

    […] but what prevents you to use nuget.org?

    The only thing is possible name collisions. I didn’t start looking into this, but it is a possibility. Otherwise I think we will end up doing this.

    • RonSijm@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      We use Azure Devops, but I would expect it to have good integration with GitHub.

      I also use Azure Devops + GitHub - What kind of integration are you looking for? I have my source in Github, and use Azure as build server

      If you’re using Azure as the build server, you can also publish your Nugets into a private feed in Azure

      • canpolat@programming.devOP
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I also use Azure Devops + GitHub - What kind of integration are you looking for?

        Not really “looking for” it but what I meant was “pushing to GitHub packages from Azure Pipelines.”

        If you’re using Azure as the build server, you can also publish your Nugets into a private feed in Azure

        That’s what we do at the moment for private feeds.

    • nibblebit@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      1 year ago

      Aah yes, naming collisions. I hadn’t considered that. I’m curious what kind packages you want to make available to the public are also prone to naming collisions that can be solved by a namespace convention. Are you publishing libraries, applications, VS extensions or templates?

      • canpolat@programming.devOP
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        We are publishing libraries (mostly client libraries). There are lots of legacy stuff. It’s safer to own the whole feed instead of pushing it to nuget.org and hoping for the best :)