{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Luminary・发光体 的问题《SignalR support in .NET 4》','https://www.manongdao.com/q-143626.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Does SignalR support .NET 4.0. Or is it support only from .NET 4.5 upwards. Is there any link which provides with minimum requirements for SignalR.
相关问题
- Carriage Return (ASCII chr 13) is missing from tex
- How to store image outside of the website's ro
- 'System.Threading.ThreadAbortException' in
- Request.PathInfo issues and XSS attacks
- How to dynamically load partial view Via jquery aj
You can download entire web stack from codeplex and SignalR from github and compile it under .net4.0
This is not the case any more, and the 2.x releases require .NET 4.5. https://github.com/SignalR/SignalR/issues/1723
The last .NET 4.0 support for SignalR is version 1.2.2. Version 2 only works with .NET 4.5
Open the NuGet Package Manager Console and type:
This will install the SignalR (Client and Server) in your selected project (web project) automatically.
The minimum requirements for SignalR is described here,
Which means your client can be WinForm/WPF application running on Windows XP.
One thing to watch here is client/server .Net versions.
Most people know (but it's worth repeating) signalR can be hosted on Windows 2008R2 upwards. Windows 2008R2 has IIS7 and thus when hosted on IIS7 signalR cannot use WebSockets (as the old Windows http stack has no support for WebSockets). So that's ServerSentEvents or LongPolling. Not great for performance.
Windows 2012 upwards (and thus at least IIS8) offers support for WebSockets, which gets the amaziong C10K perf we're all after.
Now the interesting bit.
.NET clients.
If you only care about the browser skip this bit.
So don't use signalR with WebSockets if your client is Windows7.
OR... like us you'll need to use a custom WebSocket stack coupled with WebClient to handle the http handshake.
Hopefully this will help someone else!
There is one sample project at http://www.bluelemoncode.com/2013/02/default.aspx
It is good SignalR sample and working vs 2010 sp1 and .net framework 4.0. working properly.
http://www.bluelemoncode.com/file.axd?file=2013%2f3%2fSignalR_OneOneChat.zip