How to use MVC domain model in a 4 layer project?

Question

I have a 4 layers(project) Solution.

Entity Framework Layer (EFL)
Data Access Layer(DLL): All of CRUD operations and queries.
Business Logic Layer(BLL): Calling DLL methods and adding some business to them.
MVC Layer

As I said I have a separate EFL layer and because of this I don't know How can I use benefits of models in MVC? for example I can't write validation Annotations like <required> or <Display(Name:="username:")> in EFL layer because probably they will delete if I generate model from database again. and even if I do that How I can use Model folder of MVC?

If I create some class same as EFL classes I need to write a huge bunch of code to convert these classes to each other.

As what structure I can use MVC Models? and combine them with Entity Framework classes?

Yes you need to write Model classes in Model folder

Dilip Oganiya
– Dilip Oganiya

2016-04-08 08:52:52 +00:00
Commented Apr 8, 2016 at 8:52 — Dilip Oganiya
– Dilip Oganiya, Commented Apr 8, 2016 at 8:52

L-Four · Accepted Answer · 2016-04-08 09:35:36Z

1

The M in MVC is to me the view model. This means it contains the entities that are used in your views (which are optimized for those views); which are constructed in the controllers based on the entities you receive from your business layer, and which can look completely different than the view model entities.

answered Apr 8, 2016 at 9:35

L-Four

13.6k9 gold badges73 silver badges116 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

David Osborne · Accepted Answer · 2016-04-08 12:51:04Z

Think about the following questions:

How likely is it that you will change EF for some other persistence/ORM mechanism?
How likely is it that you will change to, or want to add another front-end technology?

If your answers are that those changes are likely, then you need to isolate framework-specifics. You might do this by having a series of base classes with the framework-neutral concepts in and then having framework-specific derivatives that can be added or removed as needed. E.g. EfCustomer or HibernateCustomerRepository.

If those changes are not likely, then I would question the value that a layered approach actually provides and I wouldn't be too concerned about decorating classes with framework-specific concepts. I would aim to keep things as simple and DRY as possible.

Collectives™ on Stack Overflow

How to use MVC domain model in a 4 layer project?

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related