When multiple relationships to the same table are present the navigation properties are just postfixed with a name. We could consider using the FK name or some other means to make it clearer which is which.
This item was migrated from the DevDiv work item tracking system [ID=6053].
This work item originated from connect.microsoft.com. A member of the EF team at Microsoft should close the related Connect issue when closing this work item.
Comments: I always use a central Look-up table for my database, and this bug kills me, kindly please fix it a soon as you can, it will make the developer life much easier then when coding with navigation properties. Trying to go around it by changing name in designer (a nightmare when you update it) or add some extension properties that reference the navigation properties with incorrect naming. (extra code that is not needed and when updated the edmx sometimes it make problems too.) or change in the T4 template to generate the navigation properties, but didn't master this yet.
This item was migrated from the DevDiv work item tracking system [ID=6053].
This work item originated from connect.microsoft.com. A member of the EF team at Microsoft should close the related Connect issue when closing this work item.
Comments: I always use a central Look-up table for my database, and this bug kills me, kindly please fix it a soon as you can, it will make the developer life much easier then when coding with navigation properties. Trying to go around it by changing name in designer (a nightmare when you update it) or add some extension properties that reference the navigation properties with incorrect naming. (extra code that is not needed and when updated the edmx sometimes it make problems too.) or change in the T4 template to generate the navigation properties, but didn't master this yet.