maxmustermann/dotnet-core
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

add link tracking SymbolSource portable pdb support (#3648)

Browse source
This commit is contained in:
James May 2020-04-20 07:31:20 +10:00 committed by GitHub
parent ed3db8173a
commit 9975e5e9aa
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
Documentation/diagnostics/portable_pdb.md
View file

@ -22,7 +22,7 @@ Portable PDBs can be read on any operating system, but there are a number of pla
* Older versions of the Visual Studio debugger (versions before VS 2015 Update 2)
* Applications targeting .NET Framework 4.7.1 or earlier<sup><a href="#fn1" id="ref1">1</a></sup>: printing stack traces with mappings back to line numbers (such as in an ASP.NET error page). The name of methods is unaffected, only the source file names and line numbers are unsupported.
* C# Code analysis (aka FxCop), note that this doesn't apply to Roslyn Analyzer
* Some symbol servers (ex: SymbolsSource.org does not, nuget.org [does](https://blog.nuget.org/20181116/Improved-debugging-experience-with-the-NuGet-org-symbol-server-and-snupkg.html))
* 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://msdn.microsoft.com/en-us/library/ee8x173s.aspx)-based tools such as WinDBG.