Page Comparison

...

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 folder. 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.
   

   

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

   

   
   Your nuget package is now ready for uploading.
   

   

...