Now let’s take a look at the second situation that Entity Framework has trouble with: tables with multiple relationships. It uses a different annotation (
InverseProperty instead of
ForeignKey), but it’s no more complicated than creating a schema with a single one-to-one relationship between tables.
This is the schema we want to create.
And here are the classes we’ll need to do it.
Put On Your Thinking Hat
Ready to give ...