jprdonnelly/core
1
0
Fork 0
mirror of synced 2025-12-19 18:06:02 -05:00
Code Issues Projects Releases Wiki Activity

Learn rebrand (#8024)

Browse Source
This commit is contained in:
Maira Wenzel
2022-12-08 10:59:20 -08:00
committed by GitHub
parent 90ff62b748
commit e8eb33da7e
389 changed files with 883 additions and 883 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Documentation/diagnostics/portable_pdb.md
View File

@@ -25,7 +25,7 @@ Portable PDBs can be read on any operating system, but there are a number of pla
* Some symbol servers (ex: SymbolSource.org [does not](https://github.com/SymbolSource/SymbolSource/issues/7#issuecomment-399747015), nuget.org [does](https://blog.nuget.org/20181116/Improved-debugging-experience-with-the-NuGet-org-symbol-server-and-snupkg.html))
* Running post-compilation build step that consumes or modifies the PDB using older versions of tools such as CCI, CodeContracts.
* Using .NET decompilers such as ILDASM or .NET Reflector and expecting to see source line mappings or local parameter names.
* [MS DIA](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2015/debugger/debug-interface-access/debug-interface-access-sdk-reference)-based tools such as WinDBG.
* [MS DIA](https://learn.microsoft.com/previous-versions/visualstudio/visual-studio-2015/debugger/debug-interface-access/debug-interface-access-sdk-reference)-based tools such as WinDBG.
Over time we plan to shrink this list of non-supported scenarios so that portable PDB can become the default choice for most usage needs.