Configure the NuGet CLI to Work Opposite Artifactory as the Symbol Server

JFrog Artifactory Documentation
Products
JFrog Artifactory
Content Type
User Guide
ft:sourceType
Paligo

In addition to building and creating NuGet packages (.nupkg), the NuGet client also supports creating associated Symbol packages (.snupkg or .symbols.nupkg), that contain all the relevant symbol files for the NuGet package. The Symbol packages can be pushed to a Symbol Server, where the Symbol files can be indexed and consumed by the Visual Studio Debugger.

The Symbol package structure is similar to the NuGet package but contains the Symbol files instead of the source files.

To configure the NuGet CLI:

  1. In the JFrog Platform, navigate to Application Module | Artifactory | Artifacts.

  2. Select the NuGet repository you created,

  3. Select Set Me Up.

  4. In the Configure tab, set up the NuGet repository to work against the NuGet Client.

    Symbol_Server_CLI_configuration.png

  5. Add the following line to theNuGet.configfile.

    Configure_ NuGet.png

  6. In the Deploy tab, choose from one of the following Push options.

    • Push NuGet packages together with their related Symbol packages

      When you run the nuget push command, if there is a Symbol package present in the same directory, then the Symbol package will be automatically pushed to the same location.

      Deploying both Symbol and NuGet packages to the repo.png

      As displayed in the following example.

      nuget push mypackage.1.0.0.nupkg -Source ArtifactoryNuGetV3

  • Pushing NuGet Symbol packages only When you run the nuget push command, you can decide to push only Symbol packages by adding an ‘s’ as the prefix to the nupkg string.

    Deploying Only Symbol packages to the repo.png

    As displayed in the following example.

    nuget push mypackage.1.0.0.snupkg -Source ArtifactoryNuGetV3