What does the "Pluralize or singularize produced object names" option mean?

ado.net ado.net-entity-data-model c#-4.0 entity-framework


There is a choice to create a new Entity data Model that

[x] Pluralize or singularize generated object names

I've seen that LINQ also offers this as a choice. The ADO.NET entity framework also offers a "DEFAULT" to "pluralize or singularize produced object names," I discovered after examining it.

What happens if this option is not checked or allowed while configuring the entity data model.

What benefits, drawbacks, or problems would choosing one option over another provide for me?

11/15/2016 1:32:21 PM

Accepted Answer

It won't be an issue at all, but you may wish to do it manually. Entity set names should typically be plural and entity names should be single.

2/8/2011 5:27:37 PM

Popular Answer

If you examinePluralize or singularize generated object names in the lesson, the setcontext.cs , will have names that follow this format:

public virtual DbSet<SomeTableName> SomeTableNames { get; set; }

If not, it will be called:

public virtual DbSet<SomeTableName> SomeTableName { get; set; }

Benefits/Disadvantages in my opinion:

Collection sets should have names that finish in "s," like "dbset collection ofEmployee class of Employee Table named Employees I'll examine the option, then. However, I suppose that someone would choose to treat the database set as a table and name it the same as the table name.Employee .

Related Questions


Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow