I have an n-tier application which I have added SignalR functionality to. When I now compile my business layer I have to do a iisreset before the website can load again. It simply just keeps loading, and doesn't get anywhere. Even a kill on the w3wp process doesn't help this out.
I have tried and removed SignalR and then it works fine when compiling the backend. My guess is that a connection is made from SignalR to the server, and it is broken when the backend is compiled, which haults the site from doing a complete load.
Anything I might be able to do about this?
Sticky sessions, also known as client affinity, is not required, because clients are immediately redirected to the Azure SignalR Service when they connect.
IIS 8 or IIS 8 Express should be used for SignalR to use Web Socket and the server must be using Windows 8, Windows Server 2012 or later and the Web Socket must be enabled for the IIS.
Are you developing on windows 7? If you are then don't as it only allows 10 concurrent connections. Use IIS express instead.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With