embedding-pdb-in-exe

Set <DebugType>embedded</DebugType> in a PropertyGroup of your csproj file. The PDB data is then compiled directly into the EXE or DLL, so stack traces include file names and line numbers without a separate symbol file.

Run dotnet publish with -p:PublishSingleFile=true, --self-contained true, a RuntimeIdentifier like win-x64, and -p:DebugType=embedded. This produces one executable containing both the app and its debug symbols.

pdbonly writes symbols to a separate PDB file that must be distributed alongside the binary, while embedded stores symbols inside the EXE or DLL itself. Embedded increases file size but removes the risk of losing or mismatching PDB files.

Yes. Add the Microsoft.SourceLink.GitHub package with PrivateAssets=All, then set PublishRepositoryUrl and EmbedUntrackedSources to true alongside DebugType embedded. Debuggers can then fetch matching source from the repository.

Line numbers are missing when the build used DebugType none or the PDB file was not deployed with the binary. Verify <DebugType>embedded</DebugType> is set in the release configuration and rebuild.

Embedded PDBs contain original build machine file paths. Add a PathMap property mapping the project directory to a placeholder and enable ContinuousIntegrationBuild to sanitize paths before distribution.