Source View fails to locate source files despite valid PDB paths in dotTrace

Problem

In dotTrace Viewer, the Call Stack and Native Code views correctly resolve symbols using the configured PDB paths. However, when double-clicking a frame in the Call Stack view to open the Source View window, the profiler fails to locate the source code. This occurs even when:

• Private PDB symbols are available on the local file system (not on a symbol server).
• The rest of the viewer successfully uses the global symbol path settings to display highlighted symbols.

Resolution

To resolve this behavior, ensure that the source paths are also mapped within the Folder Substitutions settings:

1. Open the dotTrace Viewer
2. Navigate to View → Options
3. In the Options dialog, go to Source Preview → Folder substitutions.
4. Review the current values specified in the Folder Substitutions list. Check for any mappings that might point to invalid or outdated paths.
5. If the required path is missing, add a new entry mapping the source path defined in your PDBs to the actual directory on your local file system.
6. Apply the changes and reopen the Source View.