Consider the case where there is a candidate FK property by name in the dependent CLR type, but it doesn't work for the FK for some other reason--commonly, that the type of the property is not compatible with the type of the PK property. In this case we currently create a shadow property with a uniquified name--e.g. BlogId1. I assert that this is almost always not what is wanted. We should consider making this a warning, or perhaps even an error by default.