title: Dataset vs Entity Framework with stored procedures
body: <p>The whole question has been rewritten to be more clear..  </p>
  
  <p>New project design: </p>
  
  <ol>
  <li>Sql Server 2012 </li>
  <li>Visual Studio 2012 .Net 4.5</li>
  <li>Business logic will be implemented in stored procedures</li>
  <li>ASP.Net Webforms </li>
  <li>WCF SOAP XML Web Service to communicate with database using provided stored procedures by DBA</li>
  <li>Entity Framework or Dataset</li>
  </ol>
  
  <p>Here I can use Dataset - no problem, but I would like to know the advantage of Entity Framework over Dataset in more detailed explanation. I've been reading articles about entity framework, and I saw people had better experience using EF over dataset due to following reasons. </p>
  
  <p><strong>I would like to know if these are still advantages that I can obtain using EF in my case - database related actions are always done with stored procedures:</strong></p>
  
  <ol>
  <li><p>EF is a lot cleaner and much easier to maintain and program against. 
  Queries against the EF ObjectContext are always executed against the database</p></li>
  <li><p>Because the mapping between your objects and your database is specified declaratively instead of in code, if you need to change your database schema, you can minimize the impact on the code you have to modify in your applications--so the system provides a level of abstraction which helps isolate the app from the database. The EF can therefore replace a large chunk of code you would otherwise have to write and maintain yourself.(What if stored procedure design has been changed?)</p></li>
  <li><p>The EF was specifically structured to separate the process of mapping queries/shaping results from building objects and tracking changes.    </p></li>
  <li><p>DataSets suck, especially in a WCF scenario (they add a lot of overhead for handling in-memory data manipulation) -> means EF with WCF is better in performance ?</p></li>
  </ol>