This feedback came from Microsoft Connect.
The ADO.NET Entity Data Model diagram cannot properly import tables when they have no primary keys defined. I think we could add those tables in the diagram surface and let users add primary keys.
Comments: We actually do support this. We will try and infer a primary key and if we can't do that the entity will be added to the model as read-only.
The ADO.NET Entity Data Model diagram cannot properly import tables when they have no primary keys defined. I think we could add those tables in the diagram surface and let users add primary keys.
Comments: We actually do support this. We will try and infer a primary key and if we can't do that the entity will be added to the model as read-only.