Azure-devops-docs: Poor, very poor.

[Korporal]

This page is close to useless. It refers to downloading NuGet + VSTS Credential Provider - but says nothing about what to do with these once downloaded or where to put the downloaded files. I simply cannot comprehend why this publishing capability is not accessible with a few mouse clicks in the GUI, why oh why oh why is it considered acceptable to have this gap in how nuget is supported?

The article glibly refers to "run these commands" as if this was a GUI mouse click, it isn't. How do we run those commands? do I open a console window? if so where? what folder must I be in when I run the commands? What if the .exe isn't found? must I edit my path environment variable? etc, etc, etc...

I had hoped that Visual Studio 2019 would make this easy, after all it has a dedicated "Package" property window in my .Net Standard project and I can right-click a project and choose "Pack" and then...well that's it - I must then trawl the web, open power shell windows, struggle with poor documentation and fumble along. After all that I have to explain to my coworkers how I did the publish!!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: ec99483d-828e-093b-a5af-bd2d25ea27d1
• Version Independent ID: 36f67ced-654b-3cbb-2f4e-4f7b540959ba
• Content: Publish a NuGet package from the command line
• Content Source: docs/artifacts/nuget/publish.md
• Product: devops
• Technology: devops-artifacts
• GitHub Login: @elbatk
• Microsoft Alias: elbatk

[infin8x]

Thank you for the feedback. We know the experience here is way out-of-date, and the docs aren't far ahead. We're working right now on an updated design for the "Connect to feed" dialog that we hope to have rolled out (along with updated docs) by the end of Q2.

[Korporal]

@alexmullans - Thank you Alex, this is very encouraging!

[MarkSFrancis]

Would it be helpful to add links to the page for how to create and publish a NuGet package in dotnet and NET Standard and NET Framework using Visual Studio, or using the nuget CLI?

This way, someone could follow the guide to create the package, then come back to this guide to publish the package. This publish topic is only relevant immediately after following a guide to create a package, so it makes sense to link the two.

The linked articles cover both creating and publishing the nuget packages, so you'd want to only want to follow the parts that define creating the package, then come back to these docs to publish it to Azure Artifacts.

[jariwalaraj]

Agreed.

Below steps worked for me while posting a package to internal Azure Artifacts.

1. Opened Package manger in VS 2019. (had 2.2.401 installed)
2. Ran command
   PM> dotnet nuget push "Path where your .nupkg file exists" --source "Your Package source URL" -k AzureDevOps --interactive
3. It should display a unique code, which you have to provide by going to 'https://microsoft.com/devicelogin' from browser.

This should authenticate your VS for future push as well.

[bwirt]

Thanks jariwalaraj. This helped me.

[ahaynes-gw]

Thank you for the feedback. We know the experience here is way out-of-date, and the docs aren't far ahead. We're working right now on an updated design for the "Connect to feed" dialog that we hope to have rolled out (along with updated docs) by the end of Q2.

"End of Q2."-- It's September.

@jariwalaraj This didn't work for me. Instead of getting a unique code, I simply got a 401 unauthorized. "Unable to load the service index for source..."

[ramiMSFT]

@Korporal Thank you for your feedback. An updated version of the article will be deployed shortly.