Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add .pdb files to GitHub & NuGet releases
See original GitHub issueI have to debug this library and all I have is the .dll (no .pdb, so I’m unable to debug in rider). It would be nice if the pdb came with the dll so I don’t have to build it myself to be able to debug it.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Include pdb file in nuget package? · Issue #1111
Is it possible include pdb file in nuget package? thus it will be easier for VS to debug.
Read more >Include pdb files into my nuget (nupkg) files
In order to include your pdb files you just have to enter the tag <IncludeSymbols>true</IncludeSymbols> in a PropertyGroup in your project's .
Read more >5 steps to better NuGet package | Alex Klaus
Five simple but often overlooked steps to provide a better experience to the devs using your NuGet package. Consider PDBs for the Symbol ......
Read more >Debugging into a NuGet package
The first step required is to create a local NuGet folder to host the debug NuGet packages. The word local here does not...
Read more >Understanding Debugging Symbols and Using Source Link
Visual Studio has downloaded the PDB symbol files from NuGet.org in the version of the package. Once these steps has been completed, Visual ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@bruno-garcia @benaadams @samtrion
I think it was probably an issue caused by an old version of this library. I updated Rider to 2020.3.0 which did nothing, but as soon as I updated the library to 0.3.0, I immediately got my nice lovely stack traces back, and was able to debug properly. I’m now going to close this issue as I believe it is solved.
Update: I’m unable to break at most lines. The only 2 I’m able to are the beginning/entrance of the method, and the start of the
tryblock.Update 2: The debugging and breakpoints are…funky. The editor breaks but at the wrong locations:
I set the breakpoint at the entry of the
try, it supposedly broke at the entrance toSystem.Diagnostics.StringBuilderExtentions.AppendDemystified(this StringBuilder builder, Exception exception), but the stack shows thectorfor aSystem.Diagnostics.ValueTupleResolvedParameter. It also repeatedly breaks multiple times, even when the method is called only once (I’ve made sure of it).