Add the ability to step/debug through #load-ed files
I'm making heavy use of the
#load directive to include classes from other linq files. This is great since it allows me to create organized libraries of reusable code within linqpad without throwing them all in my
My Extensions file.
But currently, classes defined in a loaded file are treated as black boxes like other external references. We cannot step into the code for those classes but could jump to the definitions. It does seem to be aware of those files looking at the call stack, just can't debug it.