Where to create a data access layer in an MVC project

Question

I created an empty MVC project because I need to access the database. I do not use any entity framework, just using codes. Here I attached a snapshot of my project architecture, as you can see the Data Access Layer folder, is this a good way to use the data access level in the same project, or we need to create a separate project for the data access level.

Project architecture snapshot:

Answer 1

I also run into similar issues. Below is the help for you. http://www.codeproject.com/Articles/70061/Architecture-Guide-ASP-NET-MVC-Framework-N-tier-En

I use the repository template and unit of work. But there you encode redundancy through layers. The link above contains a bit, which one of them shows that this helps you. don't forget to make a comet about this.

Answer 2

It depends on the architecture you choose. Basically, in your MVC project, your model interacts with data.

If you use ADO , I would suggest moving model into separate class library also DataAccess to a model into separate class library that we use in 3-tier models.

Therefore, you can call data access from business logic , which are separate from the mvc project.

Something like that

In the model you can use BLL

Or you can add the App_Data folder and write a helper data access class and write business logic in the model itself. I would suggest splitting it using the first method.

Answer 3

Keep the data access level as is, but through the controller call the DataAccessLayer methods Because the view directly calls the corresponding controller. From this controller you can access the Data Access Level, but create a class (models) in the model folder