And because CSCore doesn’t provide a PDB file, that left us with no way to inspect the behavior at runtime. We also didn’t have ReSharper available to use Assembly Explorer, nor any other decompiler. Furthermore, the important properties were private so we couldn’t inspect them while debugging. Unfortunately, it was impossible to track the CSCore object’s state just by looking through the source code. Specifically, it entered a procedure containing the ominous comment: “//possible deadlock”. While hunting down a bug involving both concurrency and COM, our execution moved from our own code into that of CSCore. One of NuGet’s limitations revealed itself to me on a recent project that utilizes CSCore, a library that applies the magic of ✨abstraction✨ to COM objects, turning them into much more manageable components. I’m also grateful for package managers (which are themselves solutions to a hard problem), but neither are perfect all the time. I’m eternally grateful for open-source solutions to hard problems. This is a short guide to debugging a NuGet package by replacing it with a local build. ![]() This can make debugging packages without extra tools like ReSharper rather challenging, since you’re basically left analyzing the source code without stepping through it at runtime. NET project, but not any source or symbol files. ![]() NuGet adds and manages DLL files in your.
0 Comments
Leave a Reply. |