How to use SignalR with .net 3.5

Question

I would like to build a winform business solution using SiganlR, but I cannot install .net 4.0 on a client machine. SignalR seems to have a minimal .net 4.0 requirement. What is the best way to use SignalR from winform and .net 3.5. I would like to enable sending / receiving functions in a client application.

I will host SignalR on IIS on my intranet using .net 4.0 on the server side.

Is it possible to create an API (in .net 3.5) similar to pub # cub ? Can someone point me in the right direction.

Answer 1

If you are not too afraid to compile your own materials, I created a .NET compatible compatible client library for SignalR. It is available directly from my plug ( https://github.com/robink-teleopti/SignalR ) SignalR.

At the moment, I have no intention of making a pull request because I do not want to add this additional burden to the original project.

I have one more modification on my fork that you might be well aware of. When clients belonging to more than 20 groups, I automatically switch to using POST instead of GET, and I made small changes on the server side to handle this part.

Answer 2

I passed v1.x and v2.x SignalR to NET35 clients. Available as NuGet packages here: http://www.nuget.org/packages/Nivot.SignalR.Client.Net35/

Answer 3

One of the authors of the SignalR project had the goal of using TaskParallelLibrary (TPL), supplied in .NET 4. Therefore, I doubt that any of the C # codes from this project will be running on .NET 3.5. Why not host a WCF TCP or named-pipe WCT endpoint on the server and use regular .NET callbacks? This is relatively easy if you are running Windows Server 2008 with WAS or AppFabric.

If on an older server you can host the WebBrowser control and use the SignalR javascript client library to process the signals.

After another 6 months, I relied on my own client library, .NET 3.5, but since the support staff work on an ongoing basis, I doubt that they will have time to get support for outdated versions in the near future.