asp.net mvc - How to structure an enterprise MVC app, and where does Business Logic go?

Question

I am an MVC newbie. As far as I can tell:

• Controller: deals with routing requests
• View: deals with presentation of data
• Model: looks a whole lot like a Data Access layer

Where does the Business Logic go?

Take a large enterprise application with:

• Several different sources of data (WCF, WebServices and ADO) tied together in a data access layer (useing multiple different DTOs).
• A lot business logic segmented over several dlls.

What is an appropriate way for an MVC web application to sit on top of this (in terms of code and project structure)?

The example I have seen where everything just goes in the Model folder don't seem like they are appropriate for very large applications.

Thanks for any advice!

question from:https://stackoverflow.com/questions/2568010/how-to-structure-an-enterprise-mvc-app-and-where-does-business-logic-go

Answer 1

In my apps, I usually create a "Core" project separate from the web project.

Core project contains:

1. Business objects, such as entities and such
2. Data access
3. Anything that is not specifically designed for web

Web project contains:

1. Controllers, which route requests from the UI to the core logic
2. Views, which focus on presenting data in HTML
3. View Models, which flatten/transform core business objects into simpler structures designed to support specific views

The key point here is that the web-based Models folder/namespace is ONLY used for presentation-specific models that document the specific variables needed for a given view. As much "business logic" as possible goes into the core project.