![]() With Source Link-enabled libraries, the debugger can download the underlying source files as you step in, and you can set breakpoints/tracepoints like you would with any other source. That would be nice! In fact, the Source Link project, which was started by Cameron Taggart, realized this, and built an experience that did just that. We could have this wonderfully productive ecosystem where we could all debug with source, for all our dependencies, all the time. That means that the source I’d really like to see in my debugger is just one HTTPS GET away. Many of the NuGet libraries that we all use on a daily basis are also maintained on GitHub. NET platform is open source and maintained on GitHub. NET development practices in 2020 are a lot different and better in many ways than they were ten years ago. ![]() ![]() NET framework itself? Or you set a conditional breakpoint waiting to examine how some value got set, then noticing a call stack that’s mostly greyed out, not letting you see what happened earlier in the call stack? Wouldn’t it be great if you could easily step into, set breakpoints, and use all the debugger’s features on NuGet dependencies or the framework itself? How many times have you been in the debugger tracking down a bug, stepping through code, looking at what local variable values changed, when you hit a wall - the value isn’t what you expected, and you can’t step into the method that produced it because it’s from a library or. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |