Compatibility

Which .NET versions, EF Core versions and databases Tenantry supports, and how its package dependencies are declared.

.NET versionsCopy Anchor Link

The packages target net8.0, net9.0 and net10.0; net11.0 is added when .NET 11 is released.

Legacy means the net8.0 and net9.0 builds are still shipped, built and tested, but Microsoft stops patching .NET 8 and .NET 9, including EF Core 8 and 9, on 10 November 2026. Move to .NET 10. They stay through the beta: 1.0 ends it, not before 10 November 2027, and drops them.

EF CoreCopy Anchor Link

Each target framework's build of Tenantry.EfCore is compiled against that framework's EF Core major, and accepts any later release of it:

These minimums are the versions the tests run against. EF Core 9 on .NET 8 is not supported: use the EF Core that matches your target framework, as you would in any EF Core application.

DatabasesCopy Anchor Link

Tenantry uses only standard EF Core features, so it works with any relational EF Core provider that reports the rows an UPDATE or DELETE matched. The write-isolation suite runs against:

Details and caveats are in Tested providers.

Native AOT and trimmingCopy Anchor Link

Tenantry.Core and Tenantry.AspNetCore are trim- and Native AOT-compatible; Tenantry.EfCore is not, because EF Core is not. See AOT & trimming.

Dependency versionsCopy Anchor Link

• Microsoft.Extensions.*: a minimum from the target framework's own major (8.0 on net8.0), with no upper bound. Microsoft ships every Microsoft.Extensions major for all supported frameworks, and current Azure SDKs need 10.x even on .NET 8.
• EF Core: the target framework's major only, as above.
• Tenantry packages: Tenantry.EfCore and Tenantry.AspNetCore need exactly the same version of Tenantry.Core. Update them together.

CI checks every minimum is a version the tests run against, and a weekly job runs the whole test suite with every dependency at the newest version it allows.