Figured it out. I’m not sure why they don’t make this a built in report but maybe someday. I made a custom widget in a dashboard with Exception Description for dimension and ‘Crashes’ for the metric: Which gives me a report like this: You can also go to Customization tab and create a custom report … Read more
The purpose of a finally block is to ensure that code gets run in three circumstances which would not very cleanly be handled using “catch” blocks alone: If code within the try block exits via fallthrough or return If code within a catch block either rethrows the caught exception, or–accidentally or intentionally–ends up throwing a … Read more
It depends. If you want to provide special handling for specific errors then use multiple catch blocks: try { // code that throws an exception // this line won’t execute } catch (StackOverflowException ex) { // special handling for StackOverflowException } catch (Exception ex) { // all others } If, however, the intent is to … Read more
Usually empty try-catch is a bad idea because you are silently swallowing an error condition and then continuing execution. Occasionally this may be the right thing to do, but often it’s a sign that a developer saw an exception, didn’t know what to do about it, and so used an empty catch to silence the … Read more