1

I have:

  • DAL layer -> entities and DbContext (Entity Framework)
  • BLL layer -> services
  • UI layer -> Razor Pages

My services in BLL layer converts entities to data transfer objects and returns data transfer objects to UI layer. The UI layer also passes data transfer objects to BLL service.

Should I place data transfer objects in BLL layer or create a separate layer?

MrChudz
  • 909
  • 3
  • 10
  • 17
  • 1
    You should do what you feel best and what makes the most sense to you. There is nothing in the specs about how you should structure a solution, so this becomes a *fashion sense* question and fairly subjective. – TheGeneral Nov 25 '20 at 08:20

1 Answers1

0

Each layer should have its own Models/ViewModels.

The Persistence layer has EF Entities. Those should not surface to the upper layers. Otherwise, you'll be forever tied to EF.

The BL contains your Domain Models. The Persistence layer will take care of the mapping Entity->Domain Model (and vice-versa).

The UI has its own ViewModels and takes care of the mapping.

Now, with that said, you could manage to use Domain Model classes as EF Entities, achieving what is called "persistence ignorance". This usually requires some "magic", and is normally done by avoiding any kind of library-specific data annotation attribute on the properties (like [Table], [ForeignKey] and so on). The db mapping is handled via IEntityTypeConfiguration.

David Guida
  • 950
  • 9
  • 19