Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update portable pdb guidance in 4.7.1 #1250

Merged
merged 2 commits into from
Feb 2, 2018
Merged

Update portable pdb guidance in 4.7.1 #1250

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
6873882
Update portable pdb guidance in 4.7.1
noahfalk Feb 2, 2018
0334f61
Update portable_pdb.md
noahfalk Feb 2, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion Documentation/diagnostics/portable_pdb.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ 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.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.
* 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
* Symbol server (ex: SymbolsSource.org)
* Running post-compilation build step that consumes or modifies the PDB using older versions of tools such as CCI, CodeContracts.
Expand All @@ -29,3 +29,7 @@ Portable PDBs can be read on any operating system, but there are a number of pla

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.



<sup id="fn1">1. When running on .NET Framework 4.7.2 with an app that targets earlier .NET Framework versions we anticipate having an opt-in configuration switch as an additional mechanism to enable support for older applications<a href="#ref1" title="Jump back to footnote 1 in the text.">↩</a></sup>