Reputation: 688
I am developing a SignalR application and when something wrong happens during a SignalR call from client, I would like to propagate the exception back to the client. However, instead of sending the exception right back to the client, Visual Studio breaks on:
HubException was unhandled by user code
If I hit F5 to continue, the exception correctly propagates back to the client.
Is there a way to teach Visual Studio to just ignore certain classes of exceptions during hub execution?
This solution does not work - it catches other exceptions, but VS still breaks on the HubException: How to NOT breaking on an exception?
Upvotes: 1
Views: 210
Reputation: 2685
in a code window pres CTRL+D E to open the Exceptions window -> Add -> enter HubException and uncheck Thrown and User-unhandeled
Upvotes: 4