Using Azure Artifacts to deploy your class library
Have you ever received a nuget package from your fellow team mates and had to create a local location for that nuget package to get picked up. That is exactly what I had to deal with and the problem was, you always forget where those files are or you reset your nuget sources through a finger faux pa. I was kinda done with that and thought let me have a look, we do have an Azure DevOps instance, what would be needed? This is what I learned and how I implemented it.
Create the NuGet package
If the package that you received was just a bunch of dlls and you need to package it, have a look at this short how to to do this :)
Using Pipelines to build packages from source
Setting up a pipeline is something that you can do and this guide will get you up and running quite quickly.
To get to the point where we need we actually need to update our library so that it references
Create a Azure Artifact Feed for private NuGet Packages
Manually publish the NuGet package to the feed
- Helpful for when you donβt want to create from the source but you have a package that you can distribute.
Add NuGet source to project
Restore and run galore
π Additional Metadata
- π Type:: note
- π·οΈ Tags::
- π‘ Status:: #status/π±