I'm attempting to migrate our ASP.Net MVC application from using Signal R1.x tgo SignalR 2.x. I just found issue which will certainly cause us problems in our quest to move forward.
Our web application is MVC based and makes heavy use of the HttpContext.Current.Sessio
When running with SignalR 1.x, everything is fine and dandy with Session.
When we upgraded to SignalR 2.x, Session was suddenly null.
I did a little googling and found the following links regarding the issue:
Further investigation revealed the following tidbit of information:
HTTPContext.Current.Session is null
This behavior is by design. SignalR does not support the ASP.NET session state, since enabling the session state would break duplex messaging.
I would imagine that this will break a great many ASP .Net MVC based applications.
Is there any workaround for this?
Is this truly by design, or is it a result of using oWin::>Startup::Configurat
();} to initiate signalR in 2.x?
If possible, I’d like to figure this out and if the solution is not so painful, they will still consider moving to 2.x.
Thanks in advance for your time,