...

This article covers:

1. What the prerequisites are,.

2. How to set up your environment,.

3. How to create a NuGet package for uploading to our private NuGet feed.

4. How to upload your external dependencies to a NuGet feed.

5. How to create a project-related nuget.config file to use your feed.

Prerequisites

Anchor
prerequisites prerequisites

...

1. Gather information about the DLL. You will need the file name, a brief description, the company name, the version number of the DLL and version of .NET your application is using (usually .NET 4.7.1).
   
   The version as well as other information about the DLL can be found in the project file and in the DLL itself. First, unload the .vbproj or .csproj file in Visual Studio.
   

   

   
   Then click on the unloaded project and it will open in the editor. Find the DLLs that do not load.
   

   

   
   Locate the missing DLL file to obtain its information. The missing DLLs can sometimes be found in the dev, acc, or prod deployment folder, under the bin folder. These folders are usually indicated on the Applications page.
   

   

   Right-click and open the Properties of the DLL file to obtain its information.
   

   

2. Modify the Generic .nuspec file you downloaded from the prerequisites section above to suit the DLL file you are creating this package for, using the information gathered in step 1, entering the:
   1. Filename (without .dll)
   2. Version number
   3. Company name (or copyright information)
   4. Description
   5. The version of .NET your application is using
   

   Image RemovedImage Added

3. Save the nuspec file using the same name as the DLL file, with the .nuspec extension instead, in your artifacts folder. For example: AjaxControlTookit.nuspec.
   

   

4. Place your dependencies inside a lib\[framework short code] folder.
   

   Image Removed

   It should also be placed under the framework version short code that the library supports. For example, you should create a subfolder called net45 if your library supports .NET 4.5. This needs to correspond to the value you entered in step 2 #5.
   

   Image Added

5. From your artifacts folder, run the following command:
   nuget pack
   

   

   
   Your nuget package is now ready for uploading.
   

   

...

1. With your directory structure set up according to the above instructions, all that’s left to do is run the following command from within the artifacts folder.
   
   nuget push -Source DSD-CIVAV-Support-Feed -ApiKey az .\AjaxControlToolkit.3.5.40412.nupkg
   
   

   

   
   You will be prompted to log into Azure DevOps including approving the 2FA request, if applicable.

...

Create a Project-Related NuGet file

Anchor
nuget nuget

For projects to use the Azure Artifacts feed, you must include the following nuget.config file in the root of your project.

...

At this point you should be able to replace the missing DLL dependencies with ones from Azure Artifacts. Do so for any dependency that is missing and is not already on NuGet.

...

Troubleshooting Notes

Credentials Pop-Up

...

C:\Users\khourip\.nuget\plugins\netcore\CredentialProvider.Microsoft substituting your user folder name.

...

NuGet Errors in Visual Studio

An error we encountered is when cloning a project with spaces. NuGet does not like this. Consider removing or replacing the %20 with a - (hyphen) in your folder name.

.NET Short Codes

Anchor
net-short-codes net-short-codes

Here are some short codes that can be used as a reference. For example, .NET 4.7.2 would require a folder named net472. Here’s a shortened list.

For the full list of version numbers, see the below list:

Target Frameworks Reference for NuGet | Microsoft Docs

Helpful Links

NuGet CLI push command | Microsoft Docs

...

GitHub - microsoft/artifacts-credprovider: The Azure Artifacts Credential Provider enables dotnet, NuGet.exe, and MSBuild to interactively acquire credentials for Azure Artifacts feeds.

DSD-CIVAV-Support-Feed - Azure Artifacts

Target Frameworks Reference for NuGet | Microsoft Docs