After learning how to perform a connection and customize the transport strategy, let's move to the natural next step: calling a server-side Hub method. We are going along the same path as the one we took in Chapter 3, Using the JavaScript Hubs Client API; therefore, this recipe will match what we did in the Calling a server-side Hub method recipe in that chapter. When we compare both the recipes, we can see one big difference between them: the .NET Hubs API does not have a concept of dynamic proxy. We'll see how we can call a remote Hub using a more general-purpose API than the magical one that we saw for the JavaScript client. Such a type of generic proxy indeed exists in the context of the JavaScript client, too; we will see that in detail later in the book.