title: How to choose a data access method in ASP.NET MVC?
body: <p>I've been programming in C# 2.0 WinForms for a while now. I'm starting to get into ASP.NET and the new MVC framework and the new features of C# 3.5. I've only read a little on LINQ to SQL but have made a few test apps to try it out. In my WinForms apps, I usually had some sort of data access layer, and wrote all the SQL myself. Of course, if something can do that CRUD for me, I'm all for it.</p>
  
  <p>I followed the tutorials on the www.asp.net/mvc website and did both the Entity Framework example and the LINQ to SQL example. So far, they both seem pretty similar. LINQ feels more like SQL, but the Entity Framework feels more like C#.</p>
  
  <p>My questions are:</p>
  
  <ol>
  <li>Is one method better than the other?</li>
  <li>What are the benefits of one over the other?</li>
  <li>Is it possible to see the SQL that is generate when using either of the methods?</li>
  <li>Since I'm new to the ASP world, are web developers leaning on one side?</li>
  </ol>