Things to consider:
dotnet-ef to work with the new ASP.NET generic host builder pattern, since there is no way to update the dotnet-ef we shipped in 2.2.Another possibility: ship a 2.3 which is not in the shared framework and makes these things work.
there is no way to update the dotnet-ef we shipped in 2.2
We can update dotnet-ef: We ship a working version of dotnet-ef on NuGet that can be used with the 3.0 SDK.
We'll need to patch EFCore.Design to understand the the generic host pattern. There were some issues with patching EFCore.Design, but I don't think they'll affect projects using the 3.0 SDK.
Note: this is not a finalized plan, but rather something we want to investigate.
@ajcvickers is this no longer potentially going to happen?
We was really looking forward to using .NET Core 3 features (eg: Blazor) but we need to talk to Oracle databases, which has just been released for EF Core 2.2
@chris5287 This was a backup plan in case we were not able to deliver EF Core 3.0 by the ship date for .NET Core/ASP.NET Core 3.0. Following a review yesterday we agreed that EF Core 3.0 does not need to slip, and hence we don't need this backup plan.
That being said, it might still be worth doing this for reasons like you mention. I'll re-open to discuss with the team. However, it certainly won't happen until after 3.0 ships.
/cc @divega
We discussed this in triage and while we are not going to do anything to proactively support this, we also don't plan to do anything to block it. If people are trying to do this and things don't work, then please file issues and we will look at them on a case-by-case basis.