title: entity framework POCO + recommended patterns
body: <p>We do like EntityFramework (CTP5) quite a lot and Using it along with ASP.NET MVC3.</p>
  
  <p>What I dislike is;
  things are mixed in together.</p>
  
  <p>I can place a <strong>DisplayAttribute</strong>, <strong>RequiredAttribute</strong>, <strong>RangeAttribute</strong>, <strong>CompareAttribute</strong> together in the same class which means I am mixin in <strong>database validation</strong>, some <strong>business logic</strong> and <strong>UI</strong> alltogether. I can even place <strong>ScriptIgnore</strong> attribute to customize it as a <strong>Json DTO</strong> object. So I can use the same POCO class for Persistance, Presentation, DTO and Business Object, and as my domian model.</p>
  
  <p>Which design patterns do you follow along with EF POCO + MVC3 toolset. What layers do you have?
  What resposibilities do you add to your classes (Is Your POCO class also your Domain Model)</p>