Data Access Layer and Business Logic Layer on Separate Projects in ASP.Net MVC 3

Gostemilov

New Member
I'm currently developing a web application using ASP.Net MVC 3. I have this structure in my Solution:-WebApp Project (Models, Views, Controllers)
-Service Layer (Interfaces, Business Logics)
-Domain Project (Repositories, Interfaces, EF)
-EF4POCO Project (POCO)
Just wanna know if it's the correct way, I just to have my DATA ACCESS LAYER and BUSINESS LOGIC LAYER on separate projects. Thank you.
 
Back
Top