C # Class Names - Convention on How to Name Classes

Possible duplicate:
(Conventions) C # class names

I use the Entity framework (or even with Nhibernate or linq to sql), you usually have a series of entity classes that are passed by decision. I usually have these classes in a VS project called [SolutionName] .Data p>

At some point, they will be used by another class that can execute some business logic before saving and deleting. In this situation, I have these action classes in a project called [SolutionName] .Core

I have seen some developers suffix these classes using Logic or Manager, for example. RegistrationManager, which would then have Save (), Delete (), Update (). A prime example of this is open source NopCommerce.

Some put them in a folder called Bll, but leave the name unchanged, for example. the namespace will be [SolutionName] .Core.Bll with a class in what is called Registration. They will then respond to the namespace, distinguishing whether it is a database object or a business logic class.

The question is, how should I name classes? Should I just suffix everything with Logic / Manager / Service or is there a better solution?

+3
source share

All Articles