Symbol Packages

Symbol server URL

The symbols endpoint for your repository follows this format:

https://f.feedz.io/{organisation}/{repository}/symbols

Pushing symbols

Authentication works the same way as NuGet packages — use a personal access token as the API key.

To push the symbols package at the same time as the main package, add the -symbolSource parameter. nuget.exe will detect the symbols file automatically if it follows the PackageId.Version.symbols.nupkg naming convention:

nuget.exe push MyPackage.1.0.0.nupkg \
  -Source https://f.feedz.io/my-org/my-repo/nuget/index.json \
  -symbolSource https://f.feedz.io/my-org/my-repo/symbols \
  -ApiKey <your-token>

To push a symbols package on its own, omit -symbolSource and specify the symbols file directly:

nuget.exe push MyPackage.1.0.0.symbols.nupkg \
  -Source https://f.feedz.io/my-org/my-repo/symbols \
  -ApiKey <your-token>

Configuring your IDE

Most IDEs do not support entering credentials at configuration time for symbol servers, but will prompt when the symbol server is first accessed. Use any value for the username and a personal access token with read access as the password.

Alternatively, append your token to the symbols URL to avoid the credential prompt:

https://f.feedz.io/my-org/my-repo/symbols/<your-token>

Tools → Options → Debugging → Symbols

Add the symbol server URL under "Symbol file (.pdb) locations".
Visual Studio will prompt for credentials the first time it loads symbols.

Settings → Build, Execution, Deployment → Debugger → Symbol Servers

Add the symbol server URL. Rider will prompt for credentials on first use.

For detailed IDE configuration steps, see the Visual Studio and Rider documentation.

Searching uploaded symbols

Uploaded symbols can be searched in the Feedz portal. PDBs are uniquely identified by filename, package ID, and age. The search results show the package ID and version of the symbols package that contained each PDB.