When I generate LINQ-to-SQL classes for a table named ApplicationMenus it doesn't create a singular class for it so that the statement:
ApplicationMenu applicationMenu = new ApplicationMenu();
gives an error.
If I change the name of the table to one of these:
Menus
ApplicationMenuItems
then it correctly generates the singular class.
Why does LINQ-to-SQL have a problem with "ApplicationMenus" and what other names will cause a problem as well?