EntityFramework and other metadata

[ryan-morris]

The template works with EntityFramework because BaseEntity has an Id property that EF picks up by convention as a primary key. If you were to rename that to MyCustomPrimarykey rather than Id things start to fail at runtime with The entity type 'ToDoItem' requires a primary key to be defined..

The answer to this is usually to add a [Key] attribute to the primary key field but how would you go about doing that while still maintaining the "clean architecture" paradigm? I noticed there is a ToDoItemDTO in the Web project because of the [Required] attribute, but if you did another ToDoItemEntity you now are duplicating your model several times over if you need to annotate all of your properties for various reasons.

Is being more lax on "Duplicate Code" the best path or is there something I'm overlooking?

[camainc]

You can use the fluent API to override the default key scheme:

https://docs.microsoft.com/en-us/ef/core/modeling/keys

https://docs.microsoft.com/en-us/ef/ef6/modeling/code-first/conventions/custom

[ardalis]

What @camainc said. I prefer to do EF mapping in my DbContext or entity-specific configuration classes in the Infrastructure project.