Being able to efficiently debug through source code is a critical aspect / skillset to performing the day to day duties of a .Net developer. Typically, using Visual Studio or Visual Studio Code makes this task very easy, however, for awhile now there has been a bit of a loophole to debugging through a full project. That loophole comes to light when a project has different dependencies that were referenced as NuGet packages. That's where traditional debugging stops (since those packages are compiled binaries and not true source code on a local machine).
However, did you know there is actually a better way to handle this for certain NuGet packages? The answer my friends is SourceLink, a technology that allows you solve this issue. I recently had a chance to check this out first hand using the KenticoCloud.Delivery NuGet package since this package recently became SourceLink enabled. I mean why not, as I was doing a little maintenance on my headless CMS project anyways. Keep reading after the jump to find out how.