This occurs in CodeFirst because of the virtual keyword. In effect, you are creating a relationship where creating one item requires the creation of the other. however, the virtual keyword allows lazy instantiation, which means that creating an object of one type doesn’t automatically create the other type, allowing the Id on the foreign item to be null. This implies a 0..1 relationship, but since each side is virtual, what you get is a 0..0 which isn’t allowed.
There are 2 methods which you can use to remedy the situation.
- remove the virtual option from either one side or both sides of the navigation properties, allowing for a 0..1 or a 1..1 map.
- explicitly add a property for the Foreign key from the other entity on each object. i.e. on class
Regionadd a property for
Factoryadd a property for
There are other ways to help Entity Framework determine which object is the Dependent Object, i.e. using Entity Framework Fluent api.
Configuring a Relationship Where Both Ends Are Required (One-to-One)
In most cases the Entity Framework can infer which type is the dependent and which is the principal in a relationship. However, when both ends of the relationship are required or both sides are optional the Entity Framework cannot identify the dependent and principal. When both ends of the relationship are required, use WithRequiredPrincipal or WithRequiredDependent after the HasRequired method. When both ends of the relationship are optional, use WithOptionalPrincipal or WithOptionalDependent after the HasOptional method.
the following code would create a Principal
Factory with a Dependent
// Configure the primary key for the Region
.HasKey(t => t.RegionId);
.HasRequired(t => t.Region)
.WithRequiredPrincipal(t => t.Factory);