Debugging is not always a matter of attaching the debugger to the server code or the client code and stepping through. Sometimes, the secret is hidden in the data going back and forth and it's not that obvious to understand this with the debugger.
With logging enabled, Fiddler, the browser, and the performance counters, you should now be able to both debug and find potential bottlenecks in your system. Although, it might feel a bit primitive and different tools from what might be used to from just developing vanilla web apps, they are very detailed and should be of great assistance. Moving on, we will look at how to self-host SignalR in your own application and also how we can scale things out when there is more than one server involved, a scenario you will find yourself with typically in the cloud.