I have an application with a 3rd party framework that uses HttpContext.Current.Session. I have added changes (using disabled WebSockets) as per https://wisej.com/support/question/httpcontext-current-session-is-null to get HttpContext.Current.Session working.
This all works fine until the Application.MainPage has finished loading then the call to the 3rd party property stops working (same result as if HttpContext.Current.Session returns nothing).
Is this expected behaviour?
Please login first to submit.