Global Data Management Forum

 View Only

 IBM.EntityFrameworkCore - .NET 10 Timeframes?

Cuinn Wylie's profile image
Cuinn Wylie posted Tue November 11, 2025 05:55 PM

Hi,

I hate to be that guy, but....

Can we get an update on the plans for supporting .NET 10?

I'm aware that there is usually a release in the early months of the new year for a new .NET release, but it would be nice to get confirmation from someone.

Thanks,
Cuinn.

Lam Siew Hong's profile image
Lam Siew Hong
  • The latest official IBM NuGet package for Db2 currently targets .NET 8.0 and higher, and IBM mentions compatibility with future frameworks starting from .NET 8 onward. There’s also a note that the package can be referenced in projects using .NET 10 preview 4, which suggests IBM is preparing for .NET 10 support in upcoming releases. 

  • IBM has not yet published a formal roadmap or confirmed release date for full .NET 10 support. Historically, IBM tends to update its .NET provider early in the year following a major .NET release, but no official announcement for .NET 10 has been made so far. 

  • For now, if you need Db2 connectivity in .NET 10 preview projects, you can use the existing NuGet package since it already supports .NET 8+ and includes compatibility hooks for .NET 10 previews. 

Javier Poza's profile image
Javier Poza

Hi,

Following up on this thread with some concrete findings that may be useful for others in the same situation.

We have confirmed that IBM.EntityFrameworkCore 9.0.0.400 is not compatible with EF Core 10 final release. This goes beyond "not yet officially supported" — there are two distinct binary-level failures that make it impossible to use the package in a net10.0 project with EF Core 10.x, regardless of any configuration or workaround.

Failure 1 — occurs on context instantiation, before any query is executed:

    System.MissingMethodException: Method not found:
    'System.String Microsoft.EntityFrameworkCore.Diagnostics
    .AbstractionsStrings.ArgumentIsEmpty(System.Object)'.
    at IBM.EntityFrameworkCore.Utilities.Check.NotEmpty(...)
    at IBM.EntityFrameworkCore.Db2DbContextOptionsExtensions.UseDb2(...)

IBM.EntityFrameworkCore 9.x calls a method in Microsoft.EntityFrameworkCore.Abstractions that was removed in EF Core 10.

Failure 2 — occurs on first LINQ query execution:

    System.TypeLoadException: Method 'VisitRightJoin' in type
    'IBM.EntityFrameworkCore.Query.Internal
    .Db2SearchConditionConvertingExpressionVisitor' [...]
    does not have an implementation.
    at IBM.EntityFrameworkCore.Query.Internal
    .Db2QueryTranslationPostprocessor.Process(Expression query)

EF Core 10 added VisitRightJoin() as a new abstract method on SqlExpressionVisitor. IBM's implementation was compiled against EF Core 9 and does not implement it.

We explored assembly shims, binding redirects, and multi-targeting — none are viable in a production scenario. The only available option is to stay on a previous EF Core version, but that is a solution-wide constraint that blocks adoption of EF Core 10 for other database providers as well.

Could someone from the IBM team confirm whether a release targeting EF Core 10 is planned for Q1/Q2 2026, in line with the historical release pattern?

Thank you.

Javier Poza's profile image
Javier Poza

Hi,

Following up on this thread with some concrete findings that may be useful for others in the same situation.

We have confirmed that IBM.EntityFrameworkCore 9.0.0.400 is not compatible with EF Core 10 final release. This goes beyond "not yet officially supported" — there are two distinct binary-level failures that make it impossible to use the package in a net10.0 project with EF Core 10.x, regardless of any configuration or workaround.

Failure 1 — occurs on context instantiation, before any query is executed:

    System.MissingMethodException: Method not found:
    'System.String Microsoft.EntityFrameworkCore.Diagnostics
    .AbstractionsStrings.ArgumentIsEmpty(System.Object)'.
    at IBM.EntityFrameworkCore.Utilities.Check.NotEmpty(...)
    at IBM.EntityFrameworkCore.Db2DbContextOptionsExtensions.UseDb2(...)

IBM.EntityFrameworkCore 9.x calls a method in Microsoft.EntityFrameworkCore.Abstractions that was removed in EF Core 10.

Failure 2 — occurs on first LINQ query execution:

    System.TypeLoadException: Method 'VisitRightJoin' in type
    'IBM.EntityFrameworkCore.Query.Internal
    .Db2SearchConditionConvertingExpressionVisitor' [...]
    does not have an implementation.
    at IBM.EntityFrameworkCore.Query.Internal
    .Db2QueryTranslationPostprocessor.Process(Expression query)

EF Core 10 added VisitRightJoin() as a new abstract method on SqlExpressionVisitor. IBM's implementation was compiled against EF Core 9 and does not implement it.

We explored assembly shims, binding redirects, and multi-targeting — none are viable in a production scenario. The only available option is to stay on a previous EF Core version, but that is a solution-wide constraint that blocks adoption of EF Core 10 for other database providers as well.

Could someone from the IBM team confirm whether a release targeting EF Core 10 is planned for Q1/Q2 2026, in line with the historical release pattern?

Thank you.

Samantha Hobbs's profile image
Samantha Hobbs

Ayyy, IBM, any updates on this? What's it mean, if your company doesn't have the resources to keep up with the .NET release cycle? That's reputational harm. .NET is not some fringe ecosystem, it is one of the most important enterprise ecosystems in the industry. .NET 8 and 9 end-of-life is November. We wanna upgrade our apps to the next LTS well in advance of this. We're blocked, b/c of a dependency on DB2.

Is this the lesson we should learn?: "An IBM product (DB2) that seemed like a good idea in 2016 was no longer a support priority by 2026. Ergo: don't count on IBM products sold in 2026 being in support by 2036. If you're a developer looking to build a product with long-term support horizon, don't trust IBM."

Edit 2026-May-27: Thank you, @Yves Tilkin! Thank you IBM devs. Got it pulled, compiled, and running! And I'm happy to see that `dotnet ef optimize` works now as well! That was broken as of `8.0.0.400`, so I'm delighted that we get that functionality back in an LTS .NET version. And impressive that you released it the day after I posted. ;-) Thank you.

Yves Tilkin's profile image
Yves Tilkin

Fyi, it looks like a new version has just been published, have a look here