So, I killed literal hours today, trying to push my first NuGet package. It isn’t much, currently, it just has two extension methods for the System.DateTime object. You can find it here.
What this post aims to do is to fill the gaps that I lost hours of my life over, so that someone else doesn’t have to do the same thing. I suffered the heartache of it, let me prevent that same heartache from happening to you, yeah? 🙂
So, first things first, you need a DLL. It needs to do something. It doesn’t have to be fancy, like computing the potentiality of the quantum state of spin or anything like that. It just… …shouldn’t be an empty class and should contribute something that you think would save someone ‘x’ amount of time doing (repeatedly).
O.k., now that you have your project done, you’ll want to head over to NuGet and create an account. This just makes one of the later steps a lot easier to perform.
While you’re there, download the latest and greatest NuGet command-line tool. Copy the exe from your downloads folder to your project’s folder to make life easier for these nexts steps.
Open your choice of terminal, command or PowerShell, and navigate to where your project is. Now, run the following command, replacing the project name with the project you’ve made.
nuget.exe spec myProject.csproj
This will generate the nuspec file, which contains a list of specifications for your NuGet package.
Before you continue, open your AssemblyInfo.cs file and make the necessary changes. (Hint: When you want to bump your NuGet version, you can do that through this file).
In your nuspec file that was created, add the files section like below but targeting the .NET version of your specific assembly.
<files> <file src="..\..\Project\bin\Release\Assembly.dll" target="lib\net472" /> <file src="..\..\Project\bin\Release\Assembly.pdb" target="lib\net472" /> </files>
Also, it’s important to pick the license that’s good for your needs, so head over to SPDX’s site to see which one fits your end-goals. Once you find the license you want to use, modify your nuspec file to something like the following, specifying your chosen license instead.
When everything’s as you want it, go back to your prompt and run the following command:
nuget.exe pack myProject.csproj
This will generate the nupkg file.
Now that you have the nupkg file, go back to NuGet and, using your account that you created earlier, upload the nupkg that you just created to NuGet.
…and that’s it, you have now published an assembly to NuGet for the world to consume. 🙂