In my AspNet MVC 3 project when I try to scaffold an entity which has a One to Zero or One relationship with another entity I get “An item with the same index has already been added” error.
Essentially this happens when the Primary Key of the related table is also a Foreign Key.
At the moment my workaround is
-
Add an Id column to the related table and make it the primary key
-
Add Unique Key to the Foreign Key Column.
The problem with this is that EF will generate an ICollection navigation property for the related entity instead of just a property of the related entity type (which I can set to null in case of zero related entities)
Is this a know bug?
Am I doing something wrong?
Is there a better work around to get rid of the ICollection navigation property?
See my answer on this question:
How do I code an optional one-to-one relationship in EF 4.1 code first with lazy loading and the same primary key on both tables?
That’s the example code with the correct configuration.
You can also achieve this with DataAnnotations, but I generally prefer to keep my entity models as POCOs.