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

Answer 1

IMO this scenario is more suited to something like you'd use in WPF. ViewModel View Controller.

Your controller talks to the business services that perform functions on domain objects. The controller converts data returned from the business services (combining several if needed) into View Models (the "M" in MVC). The View Model is then passed to the View.

The same in reverse to take VM's from the view and sending the data back to the business services