Currently I have quite an extensive web application written in ASP.NET Web Forms (.NET Framework 4.8) which uses the 'old school' ASP.NET Membership Provider.
I am rewriting this application in Blazor Server. I already converted the current Membership provider to the new .NET Core Identity and this works fine in my new Blazor app. But because the migration will take a while (it's a lot!) I want to use a combination of the old app with the new.
On the authentication side this means I will need to use a common account provider, and as far as I can figure out there is no existing way to use .NET Core Identity in .NET Framework. And vice versa: I can't use the old ASP.NET Membership Provider in the new .NET 7 Blazor app.
This leads me to my question: how do I deal with this the best way? Is there an account provider that can work in both .NET Framework and Blazor simultaneously (temporarily)? Or can I use Membership provider in Blazor somehow with a workaround?
Thanks!