title: Architectural decisions: ASP.NET MVC & Entity Framework
body: <p>I'm having an architectural decision-problem:
  We're about to build a new application and we've decided we'll be using <strong>ASP.NET MVC</strong> and <strong>Entity Framework</strong> (database first probably). In the first fases we'll only be building a web application for regular browsers, but in the future we might add mobile applications. (SOA?)</p>
  
  <p>My question is now what would be the best way to build up the application architecture?</p>
  
  <p>Would this be correct?</p>
  
  <ol>
  <li>MvcProject 
  <ul>
  <li>Model </li>
  <li>View </li>
  <li>Controller </li>
  </ul></li>
  <li>DAL project 
  <ul>
  <li>Holds edmx and T4 templates</li>
  </ul></li>
  </ol>
  
  <p>I've been searching for examples, patterns and best practices but I can't seem to find something that fits just right.</p>
  
  <p>Thank you!</p>