Hey Ben, OK - I now understand what you're trying to do. Thanks.

Trapping a specific exception like this isn't usually quite the right strategy. It would be better to create an exception subclass hierarchy where we put exceptions that have more sensible messaging so we could generically pull the message and put it in the UI. Then we can progressively move the other VM exceptions into that hierarchy. There are already a few things that fall into this category