The recent Microsoft ASP.NET and Web Tools 2012.2 Update made the process of creating SignalR applications much easier within Visual Studio 2012. The update added a series of templates for designing various types of applications, one of which was a very easy to use SignalR template.
However, if you have Visual Studio 2010 and don't feel like jumping to Visual Studio 2012 then that awesome Web Tools Update didn't really apply to you at all. You shouldn't fret, because this post will cover how to get yourself up and running using SignalR within Visual Studio 2010 in a jiffy.
The Problem
You would like to play around with SignalR and all of the incredible things that it can do, but you don't want to download Visual Studio 2012 and use the awesome templates released in the Web Tools 2012.2 Update.
The Solution
There are really only 3 major steps that you'll need to take to get yourself up and running with SignalR and if you keep up with your updates, then you may only need one:
- Visual Studio 2010 Service Pack 1 - This one is a must, and you need it to actually run SignalR.
- NuGet Package Manager - You'll need to set up NuGet within Visual Studio 2010 to download SignalR (and you should want to have it anyways because it is awesome).
- Download SignalR - You can use the previous step to download the latest SignalR package from NuGet (or you can download the appropriate files directly fromSignalR).
After getting all of those up and running, you should be ready to dive into the world of SignalR. I'll review over each of the steps individually though, just for the sake of completion.
Downloading Visual Studio 2010 Service Pack 1
As previously mentioned, you'll actually need to download Service Pack 1 to run SignalR. If you are running Visual Studio 2010 anyways you should probably have it for the sake of security, bug fixes and a few additional features: Download Visual Studio 2010 Service Pack 1 Here.
Setting up NuGet
NuGet is an incredible extension to Visual Studio that allows you to easily download, install, update and manage third-party libraries within your applications. It can save you tons of time and wasted energy searching around for the "right files" and will automatically add the appropriate references to your applications. Within Visual Studio 2010, you can take the following steps to get NuGet up-and-running within your application:


Harshad PansuriyaPosted Oct 30, 2015, 1:40 AM
Nice one
Gowtham KPosted Oct 29, 2015, 1:40 PM
Thanks for sharing
Priyaranjan K SPosted Oct 29, 2015, 12:51 PM
Thanks for the Share
Nilesh JadavPosted Oct 29, 2015, 9:35 AM
Great Share sir !
Sibeesh VenuPosted Oct 29, 2015, 8:56 AM
Nice Share
Anu VPosted Oct 29, 2015, 6:53 AM
thanks