-
Notifications
You must be signed in to change notification settings - Fork 273
How does the open-sourced portable PDB from .NET team relates to this repo? #30
Comments
Portable PDB seems to be intended for CLI languages and does not offer any benefits for Visual C++ as far as I can see, so I doubt it. |
One benefit I see is it's an open specification that contributors of tools (editors, symbol converters and such) can conveniently reason about and evolve by sharing their experience and even code contributions, if VC++ also embrace it. Compared to this, classic PDB (or full-PDB as the project system team chose to call it) does not provide additional benefit and hassle for Microsoft to maintain if moving forward, portable-PDB is the way to go in .NET Core as well as .NET Framework across operating systems). |
The Portable PDB was designed to serve as a debug file format for .NET binaries for cross platform purposes. As such it has a tight coupling with concepts that can only be relied upon in those binaries and which are not present in native images. This basically makes it a non-starter for C/C++ |
Full PDBA generic symbol file format that only works on Windows but is supported by C/C++ toolchain as well as .NET Framework. Portable PDBA cross-platform, but .NET specific, symbol file format. If this is a correct understanding then I didn't knew about ".NET specific" bit. If it's so impartially .NET centric, then calling it "portable PDB" sounds like a wrong choice of name and confusing. |
yes, you are correct. Just for additional clarification, Portable PDB is PDB for .NET, and it is only targeted for .NET Core. The definition is stated here: https://github.com/dotnet/core/blob/master/Documentation/diagnostics/portable_pdb.md
|
You can use it for .net framework (not only .net core). |
https://github.com/dotnet/core/blob/master/Documentation/diagnostics/portable_pdb.md
https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PortablePdb-Metadata.md
Will VC projects ever use portable PDB?
The text was updated successfully, but these errors were encountered: