title: How should my MVC Model work with my Business logic classes?
body: <p>So I have a MVC app and in another project I have a normal collection of classes which handle the Business and Data logic for the application. I also have some logic in the Model of the MVC project itself. This logic handles ViewModels and the like, things which could not have been done in the n-tier project as they relate to the MVC project itself and need to be in the same project. </p>
  
  <p>My questions are:</p>
  
  <ul>
  <li>Should my model classes have knowledge of the n-tier business logic? Or should only the controller have this knowledge and send data back and forth between the n-tier application and the MVC model as needed?</li>
  <li>If it's ok for my model to reference the n-tier application, then should my controller access n-tier via the model class? </li>
  </ul>
  
  <p>Hope this makes sense, found it difficult to word correctly to get my point across. </p>