SignalR.Owin vs. SignalR.SelfHost
Microsoft ASP.NET SignalR Self Host still uses OWIN to startup. The only difference is that the Self Hosted SignalR server doesn't need to be nested in an ASP.NET web application hosted in IIS. It can be a simple console application.
Reasons for not hosting in IIS include:
- Environments where IIS is not available or desirable, such as an existing server farm without IIS.
- The performance overhead of IIS needs to be avoided.
- SignalR functionality is to be added to an exising application that runs in a Windows Service, Azure worker role, or other process.
I think the main difference is, that Microsoft ASP.NET SignalR OWIN is an older package, because it depends on Microsoft.AspNet.SignalR.Core (>= 1.2.2). And Microsoft ASP.NET SignalR Self Host depends on Microsoft.AspNet.SignalR.Core (>= 2.2.0). That is why I will use the Microsoft ASP.NET SignalR Self Host package.