this post was submitted on 03 Aug 2023
2 points (100.0% liked)

.NET

1502 readers
1 users here now

Getting started

Useful resources

IDEs and code editors

Tools

Rules

Related communities

Wikipedia pages

founded 2 years ago
MODERATORS
erlingur
starman
Spyros
2
Private Nuget feed hosting (self.dotnet)
submitted 1 year ago by canpolat to c/dotnet
12 comments fedilink hide all child comments
 

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?

you are viewing a single comment's thread
view the rest of the comments
[–] canpolat 3 points 1 year ago (2 children)

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.

[–] nibblebit 2 points 1 year ago (1 children)

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 2 points 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 :)

[–] RonSijm 2 points 1 year ago (1 children)

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 1 points 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.