Advice for migrating from XSD-based ADO.NET to Entity Framework (.NET Framework 4.8 -> .NET Upgrade)
Hi everyone 
I'm currently working on a progressive migration of a large ASP.NET Web Forms application (targeting .NET Framework 4.8.1) toward a modern .NET (likely .NET 9 or 8 LTS). One of the big tasks we want to tackle is replacing the existing ADO.NET data access layer, which is built using typed datasets (.xsd files), with Entity Framework.
* Ideally, we'd like to start using EF in new code while using it for the current Web Forms project (not sure if it's possible).
* We'd prefer to minimize duplicated code and avoid maintaining two separate infrastructures if possible.
My main question is: "Can a shared data access layer support both .NET Framework and .NET 8+ (maybe via an "Infrastructure" project with .NET Standard 2.0 and a specific version of EF)?
I'm currently working on a progressive migration of a large ASP.NET Web Forms application (targeting .NET Framework 4.8.1) toward a modern .NET (likely .NET 9 or 8 LTS). One of the big tasks we want to tackle is replacing the existing ADO.NET data access layer, which is built using typed datasets (.xsd files), with Entity Framework.
Key context:
* We want to keep things working under .NET Framework 4.8.1 temporarily, while gradually introducing .NET 8/9.* Ideally, we'd like to start using EF in new code while using it for the current Web Forms project (not sure if it's possible).
* We'd prefer to minimize duplicated code and avoid maintaining two separate infrastructures if possible.
My main question is: "Can a shared data access layer support both .NET Framework and .NET 8+ (maybe via an "Infrastructure" project with .NET Standard 2.0 and a specific version of EF)?
