Publish Nuget Package

For step-by-step instructions using Visual Studio and the nuget.exe CLI, see Create and publish a.NET Framework package. For.NET Core and.NET Standard projects that use the SDK-style format, and any other SDK-style projects, see Create a NuGet package using the dotnet CLI.

In this blog article, we will walk you through the process of creating your first NuGet package and show you how you can deploy it using Visual Studio. Now, let us go ahead and see how we can create and publish a NuGet package. Create a NuGet package: Create a new visual project, add a class file Build the project.
Create a class library project. You can use an existing.NET Standard Class Library project for the code you want to package or create a simple one as follows: Step 1. In Visual Studio, choose File New Project, expand the Visual C#.NET Standard node, select the 'Class Library (.NET Standard)' template, name the project ownNuGet,.
Microsoft doc: explorer: https://github.com/NuGetPackageExplorer/Nu.

NuProj adds a new project type to Visual Studio that let's you build NuGet packages.

Referencing other projects (such as C# and VB projects). This will cause their project outputs to be packaged under the lib folder. NuProj takes care of figuring out the right lib folder name, such as net45. It will also promote any NuGet referenes to proper dependencies in the resulting .nupkg file. You can also reference other NuProj projects which allows you to declare dependencies to packages that are part of the same solution.
Manual mantained content. You can also add content directly to the project. In that case, you'd simply use folders in the Visual Studio project to control how the content is packaged. For example, in order to get an install script, you'd create a tools folder and within that you'd add the install.ps1 file.
Producing symbol packages. You can easily create symbol packages. Optionally, you can also include the sources. In this case, NuProj will use the PDB information to find the source files and embed them in the resulting .nupkg file.
Build servers such as Visual Studio Online. The build integration is also available separately and can be checked in or restored as a NuGet package. For details, check out the documentation.

Please note that this is a preview. Feedback is very welcome!

A NuGet package is just a ZIP file that's been renamed with the *.nupkg extension and whose contents match certain conventions. You use nuget.exe to package that functionality into a component that can be shared with and used by any number of other developers.

Prerequisites

Install Visual Studio 2017 from visualstudio.com with any .NET-related workload. Visual Studio 2017 automatically includes NuGet capabilities when a .NET workload is installed.
Install the nuget.exe CLI by downloading it from nuget.org and add it to your PATH environment variable.
Register for a free account on nuget.org if you don't have one already.

Create Project

You can use an existing .NET Framework Class Library project for the code you want to package or create a new class library project.

In professional NuGet package, you can implement many useful features with which others can build applications.
But here we have a simple function in a class library project which will print a string on a console.

Select the Project > Properties menu command, then select the Application tab.

In the Assembly name field, give your package a unique identifier. Select the Assembly Information... button, which brings up a dialog box in which you can enter other properties that carry into the manifest (a .nuspec file).

Once all the properties are set, build the project in Release mode.

Generate Manifest (.nuspec)

You can use the nuget spec command to generate an initial .nuspec file from the project.

You run nuget spec only once to generate the initial manifest.
When updating the package, you either change values in your project or edit the manifest directly.

Open a command prompt and navigate to the project folder containing *.csproj file and run the following command.

NuGet creates a manifest that matches the name of the project, in this case, SuperLogger.nuspec. It also includes replacement tokens in the manifest.

Change Manifest (.nuspec)

NuGet produces an error if you try to create a package with default values in your .nuspec file, so you must change the following fields before proceeding.

licenseUrl
projectUrl
iconUrl
releaseNotes
tags

For packages built for public consumption, you must define Tags property, as tags help others find your package on sources like nuget.org and understand what it does.

You can also add any other elements to the manifest at this time, as described on .nuspec file reference.

Create Package

You can create a package by running nuget pack command.

NuGet generates a identifier-version.nupkg file in your project folder.

Publish Package

Once you have a .nupkg file, you publish it to nuget.org using nuget.exe with an API key acquired from nuget.org. For nuget.org you must use nuget.exe 4.1.0 or higher. To publish your package, you will need to follow the following steps.

Sign into your nuget.org account or create an account if you don't have one already.
Click on your username which is on the upper right, and select API Keys and then on webpage click on Create.

Provide a name for your key, and enter * for Glob pattern, and then click on the **Create button.

Once the key is created, select Copy to retrieve the access key you need in the CLI.

Important: Save your key in a secure location because you cannot copy the key again later on. If you return to the API key page, you need to regenerate the key to copy it. You can also remove the API key if you no longer want to push packages via the CLI.

Run the nuget push command to publish your package to nuget.org by specifying your package name and replacing the key value with your API key.

Publish Nuget Package

The nuget.exe displays the results of the publishing process, and you will see a warning because we didn't provide the license information, but that's ok.

Create Nuget Package Visual Studio