Spam and Abuse Watch

Plagiarised:

Configure package properties
Select the Project > Properties menu command, then select the Package tab. (The Package tab appears only for .NET Standard class library projects; if you are targeting .NET Framework.)
[image]
Give your package a unique identifier and fill out any other desired properties.

Source:

Configure package properties
Select the Project > Properties menu command, then select the Package tab. (The Package tab appears only for .NET Standard class library projects; if you are targeting .NET Framework, see Create and publish a .NET Framework package instead. If it doesn't appear for a .NET Standard project, you may need to update Visual Studio 2017 to the latest release.)
[image]
(... snip ...)
Give your package a unique identifier and fill out any other desired properties. For a description of the different properties, see .nuspec file reference. All of the properties here go into the .nuspec manifest that Visual Studio creates for the project.

Plagiarised:

Step 4 - Run the pack command
Set the configuration to Release
Right click the project in Solution Explorer and select the Pack command:
[image]
Visual Studio builds the project and creates the .nupkg file. Examine the Output window for details (similar to the following), which contains the path to the package file.

Source:

Run the pack command
Set the configuration to Release.
Right click the project in Solution Explorer and select the Pack command:
[image]
Visual Studio builds the project and creates the .nupkg file. Examine the Output window for details (similar to the following), which contains the path to the package file. Note also that the built assembly is in bin\Release\netstandard2.0 as befits the .NET Standard 2.0 target.

Plagiarised:

Step 5 - Publish the package
Once you have a .nupkg file, you publish it to nuget.org using either the nuget.exe CLI or the dotnet.exe CLI along with an API key acquired from nuget.org.
Acquire your API key
Sign into your nuget.org account or create an account if you don't have one already.
Select your username (on the upper right), then select API Keys.
Select Create, provide a name for your key, select Select Scopes > Push. Under API Key, enter * for Glob pattern, then select Create. (See below for more about scopes.)
Once the key is created, select Copy to retrieve the access key you need in the CLI,
Note
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.

Source:

Publish the package
Once you have a .nupkg file, you publish it to nuget.org using either the nuget.exe CLI or the dotnet.exe CLI along with an API key acquired from nuget.org.
(...snip...)
Acquire your API key
Sign into your nuget.org account or create an account if you don't have one already.
Select your user name (on the upper right), then select API Keys.
Select Create, provide a name for your key, select Select Scopes > Push. Under API Key, enter * for Glob pattern, then select Create. (See below for more about scopes.)
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.