I\'ve narrowed this down to some issue between Code First and Database first EF, but I\'m not sure how to fix it. I\'ll try to be as clear as I can, but I honestly am missin
If you have this issue with a navigation property on the same table, you'll have to change the name of our property.
For example :
Table : PERSON
Id
AncestorId (with a foreign key which references Id named Parent)
You'll have to change AncestorId for PersonId.
It seems that EF is trying to create a key ParentId because it couldn't find a table named Ancestor...
EDIT : This is a fix for Database first !