EF Core 10 support

[lauxjpn]

We will use this issue to track the progress on supporting EF Core 10, including its previews.

[witskeeper]

.NET 10 RC 1 has been released. We expect to upgrade the entire codebase to support .NET 10 and require a preview package of version 10.0.0.

Is it possible to first build an early preview version in pomelo-nightly that supports EF 10 RC and above?

[roji]

@witskeeper you can upgrade your entire codepase to .NET 10 but stay with EF 9, in case you're not aware. EF is a separate component should not be blocking a .NET upgrade.

[witskeeper]

@witskeeper you can upgrade your entire codepase to .NET 10 but stay with EF 9, in case you're not aware. EF is a separate component should not be blocking a .NET upgrade.

Yes, that works. Thank you for your suggestion.

[skoruba]

Do you plan to update to EF Core 10?
Thanks!

[ChristopheLav]

Hello @lauxjpn,

What is the plan for EF Core 10 support ? I only request some visibility about your plan.

I know EF Core 9 continue to work but some new libraries/versions depends on the EF Core 10 (Core Identity for example).

Thank you for all your hard work!

[lauxjpn]

Yes, there will be an EF Core 10 compatible version soon.

The plan is to have a working upgrade out by the time .NET 10 goes GA. Whether this will already include all new EF Core 10 features or just a subset is not clear yet.

But whatever worked in 9.0 should still work in 10.0, since we do not publish anything without ensuring that all existing tests still work.

I will open a PR for the upgrade within the next few days. It can be used to track the progress of the initial release (same as in the years before).

[sbwalker]

@lauxjpn is there a PR for tracking the progress of the .NET 10 upgrade?

[GilianK]

Sorry to push, but .NET 10 got released yesterday. Is there any ETA for a new version of Pomelo EF Core?

Using Microsoft.EntityFrameworkCore 10 with Pomelo.EntityFrameworkCore.MySql 9 does not work (I tried), it causes the following exception during application start:

System.MissingMethodException: Method not found: 'System.String Microsoft.EntityFrameworkCore.Diagnostics.AbstractionsStrings.ArgumentIsEmpty(System.Object)'.
   at Microsoft.EntityFrameworkCore.Utilities.Check.NotEmpty(String value, String parameterName)
   at Microsoft.EntityFrameworkCore.Utilities.Check.NotEmpty(String value, String parameterName)
   at Microsoft.EntityFrameworkCore.ServerVersion.Parse(String versionString, Nullable`1 serverType)
   at Microsoft.EntityFrameworkCore.ServerVersion.Parse(String versionString)
   at Microsoft.EntityFrameworkCore.ServerVersion.AutoDetect(String connectionString)

For now we will stick with version 9.0.8 of Microsoft.EntityFrameworkCore, while upgrading everything else to .NET 10. That seems to work so far.

[sbwalker]

Since my application uses the new .NET Identity in .NET 10, I get the following compilation warning:

warning NU1608: Detected package version outside of dependency constraint: Pomelo.EntityFrameworkCore.MySql 9.0.0 requires Microsoft.EntityFrameworkCore.Relational (>= 9.0.0 && <= 9.0.999) but version Microsoft.EntityFrameworkCore.Relational 10.0.0 was resolved.

It appears that both .NET Identity and Pomelo.EntityFrameworkCore.MySql have a dependency on Microsoft.EntityFrameworkCore.Relational... and only one can be the winner.