One of the most common exceptions you will hit when you first started with a SignalR chat program could look like the following:
Unhandled exception at line 78, column 13 in http://localhost:53632/home/chat
For example, if your hub class looks like the following:
And the proxy referenced in your HtmlPage1.html might look like the following:
Now this does not work since camel casing means that you need to use "myChatHub" instead. so to fix it, you can modify your client side page to use the correct casing.
Now if you would like to override this default behavior, you could add the HubName attribute to your MyChatHub class. SignalR runtime will use your name as it is, in whatever casing you like, as the name of the proxy.
Hope this helps.