Regarding extending EF Core entities and OperationalStore

[MarcHartelman]

We want to use the ef core migrations of Duende, so we are up to speed when new releases will come out.
But we also want to add some own extra properties for some specific use cases, how can we go about this.

Is it as simple as adding a new class with the inheritance of the other (duende) Entities and adding the entitytype configuration.
Or should we just implement the entire Database ourselves.

Also when trying to implement the AddOperationalStore the ef core migration errored
The table DeviceFlowCodes,
The exception 'The entity type 'DeviceFlowCodes' requires a primary key to be defined.
Do we need to add HasNoKey on the OnModelCreating

Shouldn't it be working straight out of the box ?

[RolandGuijt]

Depends on what needs to be added, but generally you should be able to use Entity Framework's standard capabilities to extend the entities and dbContext.

About your other question: Can you please check if base.OnModelCreating is called in the OnModelCreating method? If not adding it should solve your problem.

[MarcHartelman]

Okay, we can indeed use the capabilities of Entityframework, when going about the implementation, is it common practice to add both Contexts to 1 general context, or should these be implemented seperatly from eachother.

dbContext : IConfigurationDbContext, IPersistedGrantDbContext or should these be seperate at all times.

`var configurationsNamespace = $"{typeof(dbContext).Namespace}.Entities";

    modelBuilder.ApplyConfigurationsFromAssembly(typeof(dbContextr.Assembly, t => t.Namespace == configurationsNamespace);
    
    base.OnModelCreating(modelBuilder);`

Indeed the base.onmodelcreating was not called.
However,

The exception is still thrown

[RolandGuijt]

Why do you need to join the two? If the purpose is to have them in the same database just using the same connection string works too.
Did you regenerate the scheme after the OnModelCreating change?

[MarcHartelman]

I thought i saw some potential foreignkeys relating to clientid's, but i think im mistaken because they are strings.
The other reason was to keep it in the same databaseContext, but if there are reasons to keep away from that approuch we will gladly consider it.

On the second question, i removed the entire migration + folder and reran it, it still throws the error so no success there