Last post Jun 03, 2013 09:41 AM by alexsandro_xpt
May 29, 2013 03:08 PM|KevTCore|LINK
My understanding of WebSockets is that it depends on .NET 4.5 which requires VS2012 to target it. Our company has ruled out upgrading from VS2010 at this point. But we would like to utilize WebSockets when we deploy to customer servers running Windows
Server 2012. In order to utilize WebSockets, do you need to target 4.5 when you build or is it simply a matter of configuration?
May 30, 2013 03:53 AM|rstrahl|LINK
WebSockets support is only in .NET 4.5 as I understand it. SignalR only uses Web Sockets in 4.5.
If running on .NET 4.0 SignalR will fall back to long polling, forever frame etc. so it still works, but won't be using WebSockets.
+++ Rick ---
May 30, 2013 08:18 AM|KevTCore|LINK
But do you have to target 4.5 when you compile? If you target 4.0 in your app then install it on a server running 2012 Server and 4.5, will it use WebSockets?
May 30, 2013 01:37 PM|rstrahl|LINK
I think that should work yes. The 4.5 semantics are hidden inside of SignalR's core so if you run on 4.5 that should kick in. You'll have to try to be sure though but I think that would work.
May 31, 2013 09:18 AM|davidfowl|LINK
We have very detailed docs on supported platforms http://www.asp.net/signalr/overview/getting-started/supported-platforms
Jun 03, 2013 09:41 AM|alexsandro_xpt|LINK
Self-host is websocket is suported? If yes, what is necessary?