The generated PDB has issues - stackframe switching is not supported.

[sonyps5201314]

Set a breakpoint in the corresponding source code and trigger it, as shown below:

When switching the current stack frame in the Call Stack, Visual Studio fails to navigate to the C# file—even though the source code clearly exists (just like the top frame, it comes from the same ILSpy-generated C# project). Furthermore, the language type changes to "Unknown", as shown below:

However, I tested this with dotPeek and did not encounter this issue.
Moreover, it supports generating the PDB file simultaneously when generating the source project, whereas ILSpy requires generating them separately.

[sonyps5201314]

I suspect the reason is that ILSpy failed to generate valid sequence points for the lambda expression (single statement) highlighted in the image above, which prevents the stack frame from correctly supporting breakpoints.

[siegfriedpammer]

Moreover, it supports generating the PDB file simultaneously when generating the source project, whereas ILSpy requires generating them separately.

This is actually something I planned on adding after our discussion about PDBs and "logo" file header on the other thread, this allows us to produce a PDB without embedded sources.

[sonyps5201314]

Yes, I actually considered adding an option during PDB generation to control whether to include the 'Logo header copyright comment.' My original idea was to modify the save dialog or show a prompt asking the user if they wanted to include it.

A dedicated settings dialog is certainly a better approach, but it would be ideal if it could also control the PDB generation path. For example:

• Option 1: Directly use the VS SymbolCache directory, generating a structure like: D:\Win10Symbol\SymbolCache\MicrosoftPublicSymbols\Microsoft.VisualStudio.Copilot.Service.dll\35485d14b01343978673c245ea0ebbb3\Microsoft.VisualStudio.Copilot.Service.pdb. This allows VS to locate the symbols immediately.
• Option 2: A fixed directory. This is less optimal than Option 1. For it to take effect, the user must manually add this directory to VS. Furthermore, since this directory's priority will always be lower than the VS symbol cache, the user would first need to clear the corresponding PDB from the VS cache (whether it was downloaded from a symbol server or generated by the VS C# decompiler).
• Option 3: Similar to dotPeek, place it alongside the .csproj file.