From 967312d559cc129cf39d7a557b007c9b748f2922 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1=C5=A1=20Matou=C5=A1ek?= Date: Tue, 16 May 2017 09:35:52 -0700 Subject: [PATCH] Update portable_pdb.md --- Documentation/diagnostics/portable_pdb.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/diagnostics/portable_pdb.md b/Documentation/diagnostics/portable_pdb.md index b7cef1cfa..64388a539 100644 --- a/Documentation/diagnostics/portable_pdb.md +++ b/Documentation/diagnostics/portable_pdb.md @@ -20,10 +20,10 @@ Windows PDBs can only be written or read on Windows. All Windows tooling support Portable PDBs can be read on any operating system, but there are a number of places where they aren't supported yet. Here are a few – * Older versions of the Visual Studio debugger (versions before VS 2015 Update 2) -* .NET Framework prior 4.6.3: 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. +* .NET Framework prior 4.7.1: 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 * Symbol server (ex: SymbolsSource.org) -* Running any post-compilation build step that consumes or modifies the PDB, such as CCI based tools (CodeContracts) or the .NET Native compiler +* 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 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.