ASP.Net MVC and N-Tier

Posted by Damien on Stack Overflow See other posts from Stack Overflow or by Damien
Published on 2009-01-04T10:32:29Z Indexed on 2010/03/29 22:43 UTC
Read the original article Hit count: 392

Greetings,

Apologies in advance that I have not researched this toughly enough to answer the question myself, but I imagine it would take me some time and I would rather know now before I invest more time in learning it. I couldn't find anything in my initial research..

Why use ASP.Net MVC if your already using a multi-tier architecture (Data Layer, Logic Layer, Presentation Layer)? Other than the fact the controller has more power than the logic layer.

Am I right in thinking I can use nHibernate and all my data access classes, entities, and mappings in the Model part of the MVC?

When using controllers, is it best to separate a lot of the logic into a separate class so I can call it from multiple controllers? Or can I call them from the controllers themselves, considering the fact that I would not want all of them to be Actions, just normal methods.

Thanks

© Stack Overflow or respective owner

Related posts about asp.net-mvc

Related posts about n-tier