Provide method to enable LinqPad.exe to swallow exceptions
Can't safely call Write on the TextWriter provided by LinqPad's CreateXhtmlWriter when debugging. If any properties within the object being written throw an exception, the debugger catches this exception and writing ceases.
The only workarounds are to 'Continue' after each exception (which is tedious if many are thrown), or to disable CLR exceptions and then re-enable them when done.
It's not possible to have the object's properties not throw exceptions, as they are lazy loaded and will throw when certain fields are not initialised.
3
votes
Rowan
shared this idea