Sometimes, when first adopting Azure DevOps, you might find out about Azure Artifacts. With Azure Artifacts, you can host your NuGet packages (along with other package types) securely and easily. You end creating a feed. Then, it’s also easy to restore packages from your Azure DevOps pipelines.
<h2 id="heading-pre-requisites">Pre-Requisites</h2>
<ul>
<li><a target="_blank" href="https://docs.microsoft.com/en-us/azure/devops/artifacts/get-started-nuget?view=azure-devops">Create an Azure DevOps feed</a></li>
<li>NuGet CLI - I like to use [Chocolatey] to install it</li>
</ul>
<h2 id="heading-the-work">The Work</h2>
Once you have the NuGet CLI, upload a test package. Borrowing the instructions from <a target="_blank" href="https://docs.microsoft.com/en-us/azure/devops/artifacts/nuget/publish?view=azure-devops#get-or-create-a-sample-package-to-push">this MSFT doc</a> with a small modification for Azure DevOps.
<pre><code>nuget install HelloWorld -ExcludeVersion
nuget push -Source {NuGet package source URL} -ApiKey key HelloWorld\HelloWorld.nupkg
</code></pre>NuGet will probably ask you to login so that it can authenticate against Azure AD to use Azure DevOps. Once authenticated, you’ll see the package in the feed.
Lastly, you want to find the <code>.nupkg</code> file for the package you want to upload. On older .NET Framework projects, there’s usually a <code>packages</code> folder next to the solution file. If you’re moving from a self-hosted NuGet server, you might be able to fish the package from there.
Once you find the <code>.nupkg</code>, you can upload the package to Azure DevOps using the same method.
<pre><code>nuget push -Source {NuGet package source URL} -ApiKey az {your .nupkg file}
</code></pre>

Sometimes, when first adopting Azure DevOps, you might find out about Azure Artifacts. With Azure Artifacts, you can host your NuGet packages (along with other package types) securely and easily. You end creating a _feed_. Then, it’s also easy to restore packages from your Azure DevOps pipelines.

Pre-Requisites
--------------

*   [Create an Azure DevOps feed](https://docs.microsoft.com/en-us/azure/devops/artifacts/get-started-nuget?view=azure-devops)
*   NuGet CLI - I like to use \[Chocolatey\] to install it

The Work
--------

Once you have the NuGet CLI, upload a test package. Borrowing the instructions from [this MSFT doc](https://docs.microsoft.com/en-us/azure/devops/artifacts/nuget/publish?view=azure-devops#get-or-create-a-sample-package-to-push) with a small modification for Azure DevOps.

    nuget install HelloWorld -ExcludeVersion
    nuget push -Source {NuGet package source URL} -ApiKey key HelloWorld\HelloWorld.nupkg
    

NuGet will probably ask you to login so that it can authenticate against Azure AD to use Azure DevOps. Once authenticated, you’ll see the package in the feed.

Lastly, you want to find the `.nupkg` file for the package you want to upload. On older .NET Framework projects, there’s usually a `packages` folder next to the solution file. If you’re moving from a self-hosted NuGet server, you might be able to fish the package from there.

Once you find the `.nupkg`, you can upload the package to Azure DevOps using the same method.

    nuget push -Source {NuGet package source URL} -ApiKey az {your .nupkg file}

Importing a NuGet package to Azure DevOps

I am a solutions architect focusing on Kubernetes on Azure. I'm also a productivity nut. Follow me to learn more about Kubernetes or how be productive.


Facundo's Blog on Kubernetes, DevOps, Azure, productivity, and career.