Using a Private NuGet Feed in Azure DevOps Pipelines

In this quick tutorial, our teammate, Manager - Technical Support, @Progress, and Microsoft #MVP, Lance McCarthy, teaches you how to add a Service connection for the NuGet feed and use it in a .NET Core and .NET Framework build pipelines (both classic and YAML).
www.telerik.com/support
prgress.co/Azure-DevOps-Teler...

[@LanceMcCarthy]

[IMPORTANT UPDATE] When setting the URL for the feed, you will want to use our new, faster server => "nuget.telerik.com/v3/index.json" (and not nuget.telerik.com/nuget)

[@davepayne2887]

Neither one of those NuGet feeds you mentioned prompt for credentials properly in Visual Studio. It is, by far, the most frustrating thing about your product and has been an issue for us for several years. And yes, I've checked the credential cache and there aren't any telerik credentails there. Also, the agent connection did not work for me either when I tried it through our Azure DevOps pipeline. So what we end up having to do is manually copy the DLLs to the C:\Users\\.nuget\packages\telerik.ui.for.aspnet.core\2024.1.130 folder for all our team members' machines and also on the build server. It absolutely sucks. I did open a support ticket about it today.

[@telerik]

You can find Lance McCarthy's piece on the topic for additional information here: prgress.co/Azure-DevOps-Telerik-NuGet-Packages

[@rodfalanga3770]

Should the Connection Service string not have any embedded white space?

[@JasonHoningford]

Nuget Authenticate replaces this. I couldn't get it to work.

[@SpaceCorgi08]

I'm having issues on the restore task . It doesn't seem my pipline can fine the nuget.config file. I followed your steps exactly.

[@LanceMcCarthy]

Depending on what Step you're using, you might need to define the path to the config file. Here's an example that will always work because it's a pwsh command github.com/LanceMcCarthy/DevOpsExamples/blob/b957914e4edfe01448a1d8af0853dab584288338/azure-pipelines.yml#L112

[@nikola4628]

I dont understand this username/password thing? Really? But you are on the cloud. I mean that makes no sense what so ever. Is there a way to skip that? Having user/pass on the cloud is just ridiculous. On AWS all you have to to is to allow build role to access private feed. Is there something like that?