How to ship a nuget package with embedded pdbs

I was wondering, what kinds of hoops I’d have to jump through to make this work?

I have a .csproj file like this:

<PropertyGroup>
    <TargetFramework>netstandard2.0</TargetFramework>
    <DebugType>Embedded</DebugType>
    <EmbedAllSources>True</EmbedAllSources>
  </PropertyGroup>

  <PropertyGroup>
    <PackageId>Some.Sample.Package</PackageId>
    ...
  </PropertyGroup>

but when using the nuget package built from this csproj using dotnet pack and I try stepping into an API, VS asks me where to get the source file… Isn’t that supposed to be embedded?

[tmat]

Isn’t it also necessary to include: <AllowedOutputExtensionsInPackageBuildOutputFolder>$(AllowedOutputExtensionsInPackageBuildOutputFolder);.pdb</AllowedOutputExtensionsInPackageBuildOutputFolder> In the top PropertyGroup?

It is not. The project sets DebugType to embedded, which means the PDB is going to be embedded to the DLL. Furthermore, the project also sets EmbedAllSources meaning the sources are going to be embedded into the PDB. This approach is the best when the resulting size of the DLL is not an issue, as the debugger doesn’t need to find the PDB on a symbol server and the sources on the source server. Everything is embedded in a single file (the DLL).

[enzian]

Oh, actually, when I used “Step into specific” to step into the library methods then it asked me to disable “Just my Code” and then it worked! Cool!