Important!!
The SignalR server component can be hosted in the following server or client operating systems. Note that for SignalR to use WebSockets, Windows Server 2012, Windows Server 2016, or Windows 8 is required (WebSocket can be used on Windows Azure Web Sites, as long as the site's .NET framework version is set to 4.5, and Web Sockets is enabled in the site's Configuration page).
Windows Server 2016
Windows Server 2012
Windows Server 2008 r2
Windows 10
Windows 8
Windows 7
Windows Azure
Also note that for SignalR to use WebSocket, IIS 8 or IIS 8 Express must be used, the server must be using Windows 8, Windows Server 2012, or later, and WebSocket must be enabled in IIS. For information on how to enable WebSocket in IIS, see IIS 8.0 WebSocket Protocol Support.
IIS 8 or IIS 8 Express.
IIS 7 and 7.5. Support for extensionless URLs is required.
IIS must be running in integrated mode; classic mode is not supported. Message delays of up to 30 seconds may be experienced if IIS is run in classic mode using the Server-Sent Events transport.
The hosting application must be running in full trust mode.
Applications that use SignalR in browsers must use jQuery version 1.6.4 or major later versions (such as 1.7.2, 1.8.2, or 1.9.1).
SignalR can be used in the following browsers:
Microsoft Internet Explorer versions 8, 9, 10, and 11. Modern, Desktop, and Mobile versions are supported.
Mozilla Firefox: current version - 1, both Windows and Mac versions.
Google Chrome: current version - 1, both Windows and Mac versions.
Safari: current version - 1, both Mac and iOS versions.
Opera: current version - 1, Windows only.
Android browser
Unsupported Browsers
While SignalR may run without major issues in older browser versions, we do not actively test SignalR in them and generally do not fix bugs that may appear in them.