title: asp.net 5 web application with websockets on Windows 7
body: <p>I have a relatively simple web application that I am currently porting to asp.net 5. The current version runs under IIS on some Windows 7 and Server 2008 machines.
  With the next version of my software I would like to connect a C++ client via SignalR to the web application. The problem is that the current version of the new Signalr-Cpp client only supports SignalR via websockets.
  IIS on Windows 7 and Server 2008 does not support websockets, though.
  Since a self-hosting solution would be fine for me, my question is:</p>
  
  <p>Is it possible to support Signalr via websockets on Windows 7 / Server 2008 when the web app is self-hosted?</p>
  
  <p><strong>Update:</strong> </p>
  
  <p>I would accept 
  <a href="https://stackoverflow.com/questions/17957949/does-self-hosted-signalr-require-windows-server-2012-in-order-to-use-websockets">does self hosted signalr require windows server 2012 in order to use websockets?</a> as an answer if there wasn't this small comment by Damian Edwards in the following <a href="https://twitter.com/davidfowl/status/556007314692784129" rel="nofollow noreferrer">Tweet by David Fowler</a> which says </p>
  
  <blockquote>
    <p>although, with v3, websockets in a self-hosted server (like Katana) is possible</p>
  </blockquote>
  
  <p>Does this change the situation?</p>
  
  <p><strong>Final update</strong></p>
  
  <p>At least with beta 6 it works on Windows 7 when hosting the app with Kestrel and including the middleware Microsoft.AspNet.WebSockets.Server.</p>