From 9975e5e9aa12e5c3d7a2c1c3c85a064905bdbe31 Mon Sep 17 00:00:00 2001 From: James May Date: Mon, 20 Apr 2020 07:31:20 +1000 Subject: [PATCH] add link tracking SymbolSource portable pdb support (#3648) --- Documentation/diagnostics/portable_pdb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/diagnostics/portable_pdb.md b/Documentation/diagnostics/portable_pdb.md index 4971cfeb..329e376d 100644 --- a/Documentation/diagnostics/portable_pdb.md +++ b/Documentation/diagnostics/portable_pdb.md @@ -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 earlier1: 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.