NuGet CLI Usage

Use the following .NET CLI syntax to add a package to a project:

dotnet add package <package-id> \

--version <version> \

--source <repository-url>

Where,

The following example installs Newtonsoft.Json from a NuGet group:

dotnet add package Newtonsoft.Json \

--version 13.0.3 \

--source https://example.nexus.com/repository/nuget-group/index.json

Use the following syntax to restore the packages required by a project:

dotnet restore --source <repository-url>

Where <repository-url> is the NuGet v3 service-index URL or another configured NuGet source.

The following example restores packages through a NuGet group:

dotnet restore \--source https://nexus.example.com/repository/nuget-group/index.json

Publish packages directly to a NuGet hosted repository:

dotnet nuget push <package-file> \

--source <hosted-repository-url> \

--api-key <api-key>

Where,

The following example publishes a package to a hosted repository:

dotnet nuget push ./Example.Package.1.0.0.nupkg \

--source https://nexus.example.com/repository/nuget-hosted/index.json \
--api-key "$NUGET_API_KEY"

Use the following syntax to search a configured Chocolatey source:

choco search <search-term> --source="<source-name-or-url>"

Where,

The following example searches the NexusChocolatey source:

choco search git --source="NexusChocolatey"

Use the following syntax to install a package:

choco install <package-id> `

--version <version> `
--source="<source-name-or-url>"

Where,

The following example installs a package from a configured Nexus Repository source:

choco install git `

--version 2.47.1 `
--source="NexusChocolatey"

API Key needs to be associated with the hosted repository before publishing choco packages. Use the following syntax to publish a Chocolatey package:

choco push <package-file> --source="<hosted-repository-url>"

Where,

Example:

choco push .\Example.Package.1.0.0.nupkg `
--source="https://nexus.example.com/repository/nuget-hosted/"

Register Nexus Hosted Repository

Before pushing packages, register the Nexus hosted repository as a named source in your NuGet.Config using dotnet nuget add source.

For NuGet V3 hosted repository:

dotnet nuget add source "http://<your-nexus-server>:8081/repository/nuget-hosted/index.json" \
  --name NexusHosted \
  --username admin \
  --password admin123 \
  --store-password-in-clear-text \
  --configfile nuget.config

For NuGet V2 hosted repository:

dotnet nuget add source "http://<your-nexus-server>:8081/repository/nuget-hosted/" \
  --name NexusHosted \
  --username admin \
  --password admin123 \
  --store-password-in-clear-text \
  --configfile nuget.config

Upload Symbol Packages

NuGet V3 hosted repositories accepts .snupkg uploads alongside regular .nupkg uploads. The upload path is identical. dotnet nuget push uploads both .nupkg and .snupkg files if they exist side by side.

dotnet nuget push MyLibrary.1.0.0.nupkg -s NexusHosted
dotnet nuget push MyLibrary.1.0.0.snupkg -s NexusHosted

Both .snupkg downloads and SymSrv-style symbol fetches are served from a hosted repository. The .snupkg download URL requires standard repository read permissions. The SymSrv URL (/symbols/...) is served anonymously by default, since debuggers do not send authentication.

NuGet V2 hosted repositories use the legacy .symbols.nupkg format. Specify the symbol destination explicitly with the --symbol-source (-ss) flag. Without the -ss flag, the NuGet client does not know where to send the symbol package on a V2 feed.

For V2, NuGet hosted repository accepts .symbols.nupkg uploads alongside regular .nupkg uploads. The upload path is identical. dotnet nuget push uploads both .nupkg and .symbols.nupkg files if they exist side by side.

dotnet nuget push MyLibrary.1.0.0.nupkg -s NexusHosted  -ss NexusHosted
dotnet nuget push MyLibrary.1.0.0.symbols.nupkg -s NexusHosted -ss NexusHosted