snupkg format, or the default SymbolSource feed if they are legacy. When working with, the NuGet client automatically recognizes symbols packages and pushes them to NuGet server if they are in the new. symbols.nupkg symbols for more information and an example of a. pdb file, together with the source files.Ĭheck the NuGet documentation for new. Legacy symbols packages must contain both the. symbols.nupkg file with the -Symbols option. Using the nuget pack command, you can create a legacy. Nuget pack MyPackage.csproj -Symbols -SymbolPackageFormat snupkg nuspec file, including the -Symbols option: nuget pack MyPackage.nuspec -Symbols -SymbolPackageFormat snupkg If you're using the NuGet.exe., you can use the following commands to create a. Msbuild MyPackage.csproj /t:pack /p:IncludeSymbols=true /p:SymbolPackageFormat=snupkg csproj file: ĭotnet pack MyPackage.csproj -p:IncludeSymbols=true -p:SymbolPackageFormat=snupkg csproj file.Įither add this property to your.

If you're using dotnet CLI or MSBuild, you can specify SymbolPackageFormat in your. If this property is not specified, a legacy symbol package will be created. The SymbolPackageFormat property can have one of two values: symbols.nupkg (the default) or snupkg. snupkg format, you must specify the SymbolPackageFormat property. To create your symbol package in the new. On MyGet you can push both your NuGet package and its symbol package to the same feed for easier management. Using the nuget pack command, you can create a normal. Both managed and native assemblies and symbols are supported. symbols.nupkg symbols, as well as consuming symbols and source indexing. MyGet comes with its own symbol server that supports. MyGet supports NuGet symbols packages to help MyGet users debug their NuGet packages, step through their source code, and integrate with Visual Studio and tools like WinDbg. NuGet Package Manager Console PowerShell Referenceĭebugging, source code and symbols for NuGet packages.Use TFS Online Git with MyGet Build Services.Publish NuGet Packages from Azure DevOps Pipelines.MyGet and GitHub Two Factor Authentication.Checking NuGet package vulnerabilities with OWASP SafeNuGet.Make use of psake within your build scripts.Make use of nuget within your build scripts.Auto Trigger a MyGet Build using an HTTP POST Hook URL.Package not found during package restore.The source files are still in their original location.A symbols package was pushed but does not provide source stepping (legacy symbols format).Consuming symbol packages in Visual Studio.

Download symbol