My web app uses DevExpress.Blazor which is only available as a local NuGet package on my system placed there by the DevExpress installer. There is no public NuGet that has this package.
Pushing it up to GitHub as a private package, so far, appears to require that I spend several hours learning all the details of how to do this (they do not make it easy).
Is there instead a way that all these DLLs in this private NuGet can be pushed up to my project on GitHub and then be available directly when GitHub builds my app? I know that works (without having to do anything) when I publish from Visual Studio to Azure. So I'm hoping there's an equivalent for GitHub.
I'm getting closer but still struggling. First off, here's the DevExpress info on how to add their NuGet package to Azure DevOps (unfortunately they do not have instructions for GitHub).
So I've read through Working with the NuGet registry and I believe it has the information I need. But...
It is not clear which approach I should take and I don't have the in depth knowledge to make that determination myself from what is written there.
It also discusses steps without explaining how to accomplish them. For example, if I need to do the following, how do I do it?
You can publish a package to GitHub Packages by authenticating with anuget.config file, or by using the --api-key command line option withyour GitHub personal access token (classic).
Any guidance on exactly what to do appreciated.