I have a repro for what I think might be an EF bug. I would like to split one table across two entities. Each of those entites contains a reference to a third entity. The two references must be exposed with identical foreign key property names. Since they
map to columns in the same table, configuration (or, in this example, an attribute) is used to make the column names unique.
When I try to load the model, I get the above exception from EF. If I modify the name of one of the FK properties then the error goes away.
For the complete description of the problem and the source code to reproduce it, see