c# - What is the plurality naming "problem" in context of Entity Framework? -

Naming plurality in terms of entity framework What do people mean when talking about "problem"?

(again the features of the unit framework 4.0) ...

< P> Multiplying Naming

One of the major complaints in the first edition of the entity framework was that naming conventions on organizations and navigation properties such as EDM objects were used when using model wizards I went.

The first version of the unit framework was given the unit name and the unit set named the same name. There was no effort to make names uniform or authorize names when creating a model from a database. The problem is that this code causes some confusion when referencing the database table or EntityType. For example, if you have a table called employee in your database, you will also be called an entity type employee, because you are confused about whether you are referencing the table or EntityType, as in the code section below .

Customer Clients = New Customers ();

Fortunately, this issue has been addressed. The unit's data model and update model wizards offer the option to use singular or plural forms of names for both models magicians, units now, unit sets and navigation properties.

This change aims to make the application code much easier to read and avoid confusion between object names.