Summary
Currently using the System Web Adapters to share session state between Webforms app and Blazor Server app (in .net7) doesn't work at all, the session is always null on the HttpContext.
Motivation and goals
I have read the issue (#382) and understand why this is a problem, however, I need to know what are future goals of sharing session state between Webforms and Blazor apps (see next paragraphs, items 1, 2).
As mentioned in issue-382, in .net 8, when Blazor will support true (traditional) Server Side Rendering (SSR) Model, accessing the Session state will be possible. Nevertheless, there might be times, when I would like to use the Component as "Blazor Server component" by specifying the "rendermode=RenderMode.Server". In this component, I would like to access the session state from the Webforms application. The million dollar question is, are the plans to make this possible?
Is sharing Session state between Blazor app (in SSR scenario) and Webforms app be possible/available (working) upon .net 8 release? Or I have to wait for this?
Summary
Currently using the System Web Adapters to share session state between Webforms app and Blazor Server app (in .net7) doesn't work at all, the session is always null on the HttpContext.
Motivation and goals
I have read the issue (#382) and understand why this is a problem, however, I need to know what are future goals of sharing session state between Webforms and Blazor apps (see next paragraphs, items 1, 2).
As mentioned in issue-382, in .net 8, when Blazor will support true (traditional) Server Side Rendering (SSR) Model, accessing the Session state will be possible. Nevertheless, there might be times, when I would like to use the Component as "Blazor Server component" by specifying the "rendermode=RenderMode.Server". In this component, I would like to access the session state from the Webforms application. The million dollar question is, are the plans to make this possible?
Is sharing Session state between Blazor app (in SSR scenario) and Webforms app be possible/available (working) upon .net 8 release? Or I have to wait for this?