The latest articles on DEV Community by Lawrence Agbani (@raznerd). https://dev.to/raznerd https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F214660%2F342b1191-6325-47bb-a00a-3d70c43d2f56.jpg https://dev.to/raznerd en Lawrence Agbani Mon, 19 Aug 2019 10:16:33 +0000 https://dev.to/raznerd/azure-pipelines-how-to-restore-local-nuget-packages-38o https://dev.to/raznerd/azure-pipelines-how-to-restore-local-nuget-packages-38o <h3> Why would I want to restore local nuget packages? </h3> <p><em>Please note that it is recommended to pack and <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/nuget?view=azure-devops#push-nuget-packages">publish all packages</a> and reference them by adding the URL as a new packageSource in your Nuget.config</em></p> <p>With that out of the way, there might be times when you have local <code>.nupkg</code> packages and wish to restore these packages during the build stage in your Azure pipeline. In my case, I had to quickly setup Azure pipeline for a client and they were still figuring out their private nuget package repository, so I set it up in such a way that it was possible for them to add the new package repository URL when they were done.</p> <h3> What problems will I encounter? </h3> <p>For the purpose of this article, I’ll be using the <code>azure-pipeline.yml</code> file method (instead of the GUI method). In your <code>azure-pipeline.yml</code> file, you might have something that looks like this:

</p> <div class="ltag_gist-liquid-tag"> </div> <p>With the above, if you only have referenced packages from api.nuget.org, the build pipeline should run fine. However, the moment you add references to local packages, you’ll get an error that looks like this:<br> <br> 
<br> <code>
error NU1101: Unable to find package Company.Connect.Shared.Logging. No packages exist with this id in source(s): nuget.org Build failed
</code><br> </p> <h3> How can I solve the problem? </h3> <p>That’s why you’re here, right? To solve this problem, you need to add an extra step to your azure-pipeline.yml file called the the <code>Restore</code> step before your <code>Build</code> step. Now your azure-pipeline.yml should look like this:</p> <div class="ltag_gist-liquid-tag"> </div> <p>With this, your Azure pipeline first does a <code>dotnet restore</code> fetching all packages including the local ones before going ahead to <code>build</code>. At this time, during build, the local packages will then be available.</p> <p>Thanks for reading :D</p> azure azurepipelines dotnet dotnetcore