DevOps for ASP.NET Developers: Hosting NuGet Packages

NuGet defines how packages for .NET are created, hosted, and consumed, and provides the tools for each of those roles. Using NuGet feeds, you can make your packages publicly available or limit them to an audience, such as your internal team.
In this episode, Abel shows Jeremy some different options for publishing and hosting your own NuGet packages.
[00:38] - Versioning dependencies with NuGet
[02:47] - Creating NuGet packages basics
[03:54] - Setting up a package feed in Azure DevOps Artifacts
[05:05] - Building packages in Azure DevOps Pipelines
[08:47] - Publishing and hosting NuGet feeds to GitHub
NuGet Package creation workflow
docs.microsoft.com/nuget/crea...
Publishing NuGet packages
docs.microsoft.com/nuget/nuge...
GitHub Packages
github.com/features/packages

[@jonsagara]

You mentioned a tool at ~13:15. Symversion? Do you have a link to it?

[@danguthrie261]

Any tips on debugging? If the shared library source is just “passed from project to project” the shared code project is in the same solution and it’s trivial to debug. When leveling up to sharing with packages, is it possible to accomplish anything similar?

[@Kowabrass]

Rest in peace, Abel!

[@xnishd]

i see what you did there