Managing errors across a complex asynchronous workflow

In the last recipe of the chapter, as we did in Chapter 3, Using the JavaScript Hubs Client API, we'll learn how to handle errors occurring during all the possible SignalR operational steps and connection states.

The HubConnection class from the .NET client offers a specific Error event, which is useful to manage most of the exceptions raised by SignalR itself, whereas any server-side exception occurring during a Hub method invocation can be trapped simply by surrounding the client-side invocation in a try...catch block. We'll talk a little bit more about the latter case while commenting on the code of this recipe.

Getting ready

Before proceeding with this recipe, please remember to start the server application that we used in the homonymous recipe called Managing errors across a complex asynchronous workflow from Chapter 3, Using the JavaScript Hubs Client API. This is because our code will connect to its Hub, whose method is already randomly...