title: Entity Framework classes vs. POCO
body: <p>I have a general difference of opinion on an architectural design and even though stackoverflow should not be used to ask for opinions I would like to ask for pros and cons of both approaches that I will describe below:</p>
  
  <p>Details:
  - C# application
  - SQL Server database
  - Using Entity Framework 
  - And we need to decide what objects we are going to use to store our information and use all throughout the application</p>
  
  <p>Scenario 1:
  We will use the Entity Framework entities to pass all around through our application, for example the object should be used to store all information, we pass it around to the BL and eventually our WepApi will take this entity and return the value. No DTOs nor POCOs.</p>
  
  <p>If the database schema changes, we update the entity and modify in all classes where it is used.</p>
  
  <p>Scenario 2:
  We create an intermediate class - call it a DTO or call it a POCO - to hold all information that is required by the application. There is an intermediate step of taking the information stored in the entity and populated into the POCO but we keep all EF code within the data access and not across all layers.</p>
  
  <p>What are the pros and cons of each one?</p>