Skip to content
Discussion options

You must be logged in to vote

That seems like a proper solution. Unfortunately there is a change between EF Core 8.0 and 9.0 that is not breaking at the code level, but does cause a binary breaking change (dotnet/efcore#35105).

Working around this would not be trivial (we tried a few approaches all with different drawbacks). We'd recommend right now to use IdentityServer with EF Core 8 on net8, and IdentityServer with EF Core 9 on net9 (or as you did, implement another solution).

We'll likely change the dependency definition in a future IdentityServer release.

Replies: 2 comments 27 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
27 replies
@maets
Comment options

@maartenba
Comment options

@maets
Comment options

@maartenba
Comment options

Answer selected by maartenba
@FDonald
Comment options

@maartenba
Comment options

@FDonald
Comment options

@maartenba
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
5 participants