How to Push Data from Server to Client Using SignalR

In real-time environments the server is aware of the data updates, event occurrences, etc. but the client doesn’t know it unless the request is initiated by the client to the server seeking the updates. This is commonly achieved through methods like continuous polling, long polling, etc. and these methodologies incur a lot of traffic and load to the server.

The alternate approach to simplify and reduce the overhead is to make the server capable of notifying the clients. There are many technologies introduced to achieve this and some of them are WebSockets, SSE (Server Sent Events), Long polling, etc. Each of these methods has its own caveats like WebSockets are supported only on browsers that support HTML5 and SSE is not supported on Internet Explorer.

SignalR is an Asp.Net library, which is designed to use the existing transport technologies underneath based on the client nature and the support it offers. SignalR is capable of pushing the data to a wide variety of clients such as a Web page, Window application, Window Phone App, etc. The onus is now removed from the developers of worrying about which server push transport to use and deciding on the fallbacks in case of unsupported scenarios.

Composition of SignalR

To start with SignalR it is important to know the components. The server part of the SignalR technology requires hosting a PersistentConnection or a SignalR hub.

1. PersistentConnection – This is a server endpoint to push the messages to the clients. It allows the developers to access the SignalR features at a low level.

2. Hub – It is built on top of the PersistentConnection exposing high-level APIs and it allows the developers to make the server to client calls in an RPC fashion (Remote Procedure Call).

On the client front SignalR offers different client libraries to different clients like Windows App, Web Form, Windows Phone, iOS, Android, etc. The clients have to make use of the client libraries to get connected to the SignalR hub. These client libraries are available as NuGet packages.

Fig 1.0 shows a basic SignalR environment

Basic SignalR Environment
Fig 1.0: Basic SignalR Environment

Sample Application

Let us build a sample chat application that broadcasts the messages to all connected clients or to particular groups. In this example consider the clients to be a Windows application and a web form client.

Creating an Asp.Net SignalR Hub

Open Visual Studio and create an empty MVC application named MyChatApplicationServer. Now open the NuGet packages, search and include Microsoft ASP.NET SignalR.

Now right click on the project, add the SignalR Hub class and name it as MyChatHub.  Add the following code to the class.

    public class MyChatHub : Hub
        public void BroadcastMessageToAll(string message)
        public void JoinAGroup(string group)
            Groups.Add(Context.ConnectionId, group);
        public void RemoveFromAGroup(string group)
            Groups.Remove(Context.ConnectionId, group);
        public void BroadcastToGroup(string message, string group)

The HUB class also provides the properties Clients, Groups, Context and events like OnConnected, etc.

Finally you should also add Owin startup class to map the available hubs as shown below.

[assembly: OwinStartup(typeof(MyChatApplicationServer.Startup))]
namespace MyChatApplicationServer
    public class Startup
        public void Configuration(IAppBuilder app)

Pushing Data to a Web Form Client

Now create a web form client project named WebClient and add a simple HTML file ChatWebClient.html with the following code. Add the references to the required script files.

<!DOCTYPE html>
<html xmlns="">
    <script src="Scripts/jquery-1.6.4.min.js"></script>
    <script src="Scripts/jquery.signalR-2.0.1.min.js"></script>
    <script src="http://localhost:32555/signalr/hubs/" type="text/javascript"></script>
    <script type="text/javascript">
        $(function () {
            var myChatHub = $.connection.myChatHub;
            myChatHub.client.newMessageReceived = function (message) {
                $('#ulChatMessages').append('<li>' + message + '</li>');
            $.connection.hub.url = "http://localhost:32555/signalr";
            $.connection.hub.start().done(function () {
                $('#btnSubmit').click(function (e) {
                    myChatHub.server.broadcastMessageToAll($('#txtEnterMessage').val(), 'Web user');
            }).fail(function (error) {
        <label id="lblEnterMessage">Enter Message: </label>
        <input type="text" id="txtEnterMessage" />
        <input type="submit" id="btnSubmit" value="Send Message" />
        <ul id="ulChatMessages"></ul>

There are two ways of implementing the client function one with proxy and other without. The above example is the one without a proxy.

In the connection start you may also mention which transport SignalR should use.

Pushing Data to a Windows Application Client

Let us add a windows app and subscribe to the SignalR host. Create a new windows application named WinFormClient and from the nugget packages install Microsoft ASP.NET SignalR .NET client package. In the Program.cs add the following code.

namespace WinFormClient
    public partial class Form1 : Form
        HubConnection hubConnection;
        IHubProxy hubProxy;
        public Form1()
            hubConnection = new HubConnection("http://localhost:32555/signalr/hubs");
            hubProxy = hubConnection.CreateHubProxy("MyChatHub");
            hubProxy.On<string>("newMessageReceived", (message) => lstMessages.Items.Add(message));
        private void btnSubmit_Click(object sender, EventArgs e)
            hubProxy.Invoke("BroadcastMessageToAll", textBox1.Text, "Window App User").Wait();

Once done go ahead and run both the web and Windows client. Enter the messages and look at how the message is getting pushed across both the clients though they are of a different nature. Fig 2.0 shows a sample screenshot.

Web and Windows Clients
Fig 2.0: Web and Windows Clients

SignalR is capable of serving multiple connected clients irrespective of the client platform or technology. I hope this article provides a good amount of information about pushing data from the server to client using Asp.Net SignalR. Happy reading!

Related Articles


  • Error

    Posted by Shahid on 10/13/2014 12:23am

    which dll/namespace i need to add for this: HubConnection hubConnection; IHubProxy hubProxy; i added these but it not work using Owin; using Microsoft.AspNet.SignalR; using Microsoft.AspNet.SignalR.Hubs;

  • Signal R windows application

    Posted by prakash on 09/24/2014 03:10am

    hi, im trying to develop this project im getting this error connection is not established please tel me where i did the mistake.please do needful

  • Can i add both web and window in one Solution ?

    Posted by Egy Developer on 04/18/2014 04:37am

    Hi Thanks for that great effort of that lesson, But can i add the both web form and the window form at one solution and they can chat real time together? Please if that applicable how can i do that, and if you had this solution before send me it, i need it cauz am new with SignalR :) Thanks

  • Im trying to have a admin control

    Posted by kishore on 03/04/2014 09:07pm

    Im trying to have a admin control in my signalr chat application where admin can delete any unwanted messages and after validating the message he can transfer the message to the public posting. so what should i do for cancelling the messages. this is the link from which im trying to embed the admin control.

  • lstMessages missing in WinFormClient

    Posted by Varma on 01/23/2014 11:26am

    Its pretty good article for beginners. I followed it step by step but got build error. Please provide/declare the "lstMessages" in WinFormClient

    • Reply

      Posted by Author on 01/29/2014 03:21am

      lstMessages is a listbox control's id. It is to bind the pushed messages on the win form.

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • As SIP explodes beyond connecting VoIP calls to a plethora of communication modes, now, more than ever, hyper connected Contact Centers must quickly adopt and implement the highest measures of security to ensure an entirely new level of protection.

  • Providing superior IT solutions not only differentiate VARs from their competitors, this practice also establishes a foundation of trust upon which a VAR can build a lasting advisor relationship with its customers. VARs who settle for mediocre AV products ultimately encourage customers to view the VAR as equally undistinguished. Delivering truly exceptional endpoint security – thus building credibility and trust with the VAR's customers – demands a fundamentally new approach. Read this white paper …

Most Popular Programming Stories

More for Developers

RSS Feeds

Thanks for your registration, follow us on our social networks to keep up-to-date