Upon experimenting with various methods of creating NuGet packages manually and otherwise, I find this process quite straight forward and easy. This involves using a template created by Danny Varod. The following are the step-by-step process to be followed

But if you'd like something a little more professional, you can create a NuGet Web site. It's easy to do: First, in Visual Studio, create an Empty Web Application. Once the project appears in Solution Explorer, right-click on it and select Manage NuGet Packages. In the NuGet Package Manager, do a search for the NuGet.Server package and install it. It's a simple process to create a NuGet package from a.NET Standard Class Library in Visual Studio on Windows, and then publish it to nuget.org using a CLI tool. Note If you are using Visual Studio for Mac, refer to this information on creating a NuGet package, or use the dotnet CLI tools. Let’s create another client project using Visual Studio. Right click on the project, and go to Manage NuGet Packages for Solution Click the Settings button (little gear icon) next to the.

Get the template if you haven’t already
Install the visual studio extension that adds the NuGet package template to your Visual Studio

Create Project Using the NuGetPackage.Project.NuGet template

In the project, you will find the following files

internalpackages.config
NuGetPack.config
packages.config

For Starters, the below extract from the readme.txt file is quite explanatory
1. You can modify the package metadata by editing NuGetPack.config.
2. To include projects in this package, add project references to this project.
3. To include dependencies on external NuGet packages, add NuGet package references to this project.
4. To include dependencies on other NuGet packages created in this solution, add them to the internalPackages.config file.
5. To synchronize the package version with the version of the assemblies included in it, use a shared AssemblyInfo.cs file for the source projects and the NuGet package projects.
6. To add system reference to the package, add them as references to this project and set AddFrameworkReferences to true in the config file.

Add the required assembly, its dependencies to the project
We can now add the library as reference like we normally do, either from a project, a standalone assembly file(dll etc.) or via NuGet Package Manager. Wd my passport driver for mac os. Once done it would look something like this

Edit the Metadata for the package
Edit the file NuGetPack.config and update description, summary, logo, website etc. This is what will be shown on the NuGet Package manager modal/console.

<NuGetPack>
<AddFrameworkReferences>false</AddFrameworkReferences>
<IconUrl>https://pramodmohanan.net/my-favicon.ico</IconUrl>
<ProjectUrl>https://pramodmohanan.net/</ProjectUrl>
<LicenseUrl>https://pramodmohanan.net/my-license-page</LicenseUrl>
<Authors>Pramod Mohanan</Authors>
<Owners>Pramod Mohanan</Owners>
<Copyright>My Copyright Line</Copyright>
<Description>This is sample library created for my blog post</Description>
<Summary>Adds My Library to your project. This library was created as a sample for my blog post. However it has a class with helloworld function :)</Summary>
<Keywords>MyLibrary, HelloWorld</Keywords>
</NuGetPack>

Install the PubComp.NuGetPack in your project
In Nuget Package Manager, look for PubComp.NuGetPack by Danny Varod and install it. This should add a folder with NuGet.exe and NuGetPack.exe which is used for creating the package post the compilation. (Check the post-build event command line project properties – it uses these files). Once installed it looks like this in the solution explorer

Build the Project using Release (Any CPU) configuration
After building the package you should see the .nupkg file in your release folder. This is the nuget package ready to go into any Nuget repository.

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

Create Nuget Package Visual Studio 7

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.

Lippert schwintek slide manual. NuGet generates a identifier-version.nupkg file in your project folder.

Create Nuget Package Visual Studio Mac

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 do