{"id":139,"date":"2018-11-16T00:00:00","date_gmt":"2018-11-16T08:00:00","guid":{"rendered":"http:\/\/devblogs.microsoft.com\/nuget\/improved-debugging-experience-with-the-nuget-org-symbol-server-and-snupkg"},"modified":"2018-11-16T00:00:00","modified_gmt":"2018-11-16T08:00:00","slug":"improved-package-debugging-experience-with-the-nuget-org-symbol-server","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/improved-package-debugging-experience-with-the-nuget-org-symbol-server\/","title":{"rendered":"Improved package debugging experience with the NuGet.org symbol server"},"content":{"rendered":"

Starting today, you can publish symbol packages to the NuGet.org symbol server. With NuGet.org as a single service provider for libraries and symbols, package authors and consumers will have a streamlined publishing and consumption experience. With a single place for managing authentication and identity, you can be sure that both the package and its symbols are coming from the same author when you consume a NuGet package from NuGet.org.<\/p>\n

Publish a snupkg to the NuGet.org symbol server today!<\/h2>\n

We have introduced a new symbol package format – .snupkg<\/code>. You will need Visual Studio 2017 15.9<\/a> to generate portable PDBs<\/a> that can be packaged as .snupkg<\/code> for publishing to the NuGet.org symbol server.<\/p>\n

Create and publish snupkg to NuGet.org<\/h3>\n
    \n
  1. \n

    Compile your code using Visual Studio 2017 15.9<\/a> to generate the portable PDBs.<\/p>\n<\/li>\n

  2. \n

    Get nuget.exe 4.9.0<\/a> \/ dotnet.exe 2.1.500<\/a> or higher (Visual Studio 2017 15.9 ships with dotnet.exe 2.1.500 and msbuild).<\/p>\n<\/li>\n

  3. \n

    Create the .snupkg using pack with your tool of choice. We have added a new property SymbolPackageFormat<\/code>, which must be set to snupkg<\/code><\/p>\n

    using dotnet<\/strong><\/p>\n

    > dotnet pack MyAwesomeLib.csproj --include-symbols -p:SymbolPackageFormat=snupkg<\/code><\/p>\n

    using nuget<\/strong><\/p>\n

    > nuget pack MyAwesomeLib.nuspec -Symbols -SymbolPackageFormat snupkg<\/code><\/p>\n

    using msbuild<\/strong><\/p>\n

    > msbuild \/t:pack MyAwesomeLib.csproj \/p:IncludeSymbols=true \/p:SymbolPackageFormat=snupkg<\/code><\/p>\n<\/li>\n

  4. \n

    Push the .nupkg to NuGet.org (we will detect the .snupkg and push it for you)<\/p>\n

    using dotnet<\/strong><\/p>\n

    > dotnet nuget push MyAwesomeLib.1.0.0.nupkg -s https:\/\/api.nuget.org\/v3\/index.json -k ~~your API key here~~<\/code><\/p>\n

    using nuget<\/strong><\/p>\n

    > nuget push MyAwesomeLib.1.0.1.nupkg -Source https:\/\/api.nuget.org\/v3\/index.json -apikey ~~your API key here~~<\/code><\/p>\n

    using nuget.org upload<\/strong><\/p>\n

    \"nuget.org<\/p>\n<\/li>\n

  5. \n

    Once validated and indexed, the .snupkg<\/code> will be available for consumption and will also be downloadable from the NuGet.org gallery.<\/p>\n

    \"snupkg<\/p>\n<\/li>\n<\/ol>\n

    \n

    NuGet.org symbol server only accepts the new symbol package format .snupkg<\/code>. Take a look at NuGet.org symbol package constraints<\/a> for more info.<\/p>\n<\/blockquote>\n

    Consume snupkg from NuGet.org in Visual Studio<\/h3>\n

    You will need Visual Studio 2017 15.9<\/a> to consume .snupkg<\/code> from NuGet.org symbol server.<\/p>\n

      \n
    1. \n

      In Visual Studio, open Tools<\/strong> > Options<\/strong> > Debugging<\/strong> > Symbols<\/strong> (or Debug<\/strong> > Options<\/strong> > Symbols<\/strong>).<\/p>\n<\/li>\n

    2. \n

      Under Symbol file (.pdb) locations<\/strong>, add a new symbol server location by selecting the +<\/strong> symbol in the toolbar. Use the following URL https:\/\/symbols.nuget.org\/download\/symbols<\/code>.<\/p>\n

      \"VS<\/p>\n<\/li>\n<\/ol>\n

      FAQs<\/h2>\n