Using System.Web Adapters to Share Session State in ASP.NET Upgrade Scenarios [11 of 18] Migrating

preview_player
Показать описание
In this video, Mike uses System.Web adapters to share session state between an original ASP.NET app and a new ASP.NET Core app that he is incrementally migrating the endpoints to from the original app. Using this shared session solution, session state is preserved even if users hit some endpoints in the old app and some in the new app.

Series:

Chapters:
00:00 - Intro
01:25 - Using System.Web.Adapters in views
03:00 - Options for sharing session state between projects
04:40 - Configuring session sharing using System.Web.Adapters
11:30 - Congiguring session serialization
13:10 - Configuring session sharing in controllers and views
16:20 - Migrating additonal controllers after session sharing is configured
18:50 - Showing side-by-side session data sharing

Follow Mike:

Links:

#dotnet #upgradeassistant #aspnetmvc
Рекомендации по теме
Комментарии
Автор

Why share session state? Eventually we will not have net framework project .What if we want to migrate session state to core completely.

viralpatelv
Автор

Unfortunately we're struggling with a null session in our .NET 8 MVC app. We can see it working on the WebForms app, but somewhere the sharing between the two is breaking down.

Honz
Автор

Is there a way to have multiple RemoteAppURL or a Wildcard URL Scheme for RemoteAppUrl?

brainzhacked
Автор

Hey good work. Can this be possible from web forms to .NET Core?

belfastroamer
Автор

This all seems overly complicated. Maybe it's better to start from scratch?

ricks
Автор

"And now it should work." *doesn't work* - Ahhh yes :D Sounds just like my 10th commit message trying to fix a bug :P

TopSwagCode