guide :
http://weblogs.asp.net/scottgu/code-first-development-with-entity-framework-4
Entity Framework vs LINQ to SQL
source http://stackoverflow.com/a/32319137/1320686
LINQ to SQL - Created by C# team
Entity Framework - Created by SQL Server team
Microsoft Entity Framework (Part1 of 6) by thousandtyone
https://www.youtube.com/watch?v=BS6IKdUd2V8
sample of 'code behind' :
James DeMeuse wrote (http://stackoverflow.com/a/28353126) :
https://github.com/jdemeuse1204/OR-M-Data-Entities
http://ormdataentities.com/
http://weblogs.asp.net/scottgu/code-first-development-with-entity-framework-4
Entity Framework vs LINQ to SQL

source http://stackoverflow.com/a/32319137/1320686
LINQ to SQL - Created by C# team
Entity Framework - Created by SQL Server team
source http://stackoverflow.com/a/8641555/1320686Sqlmetal.exe generated file is used in Linq to SQL (ORM)
where
EDMGen.exe tool generated file is used in EntityFramework (ORM).
Microsoft Entity Framework (Part1 of 6) by thousandtyone
https://www.youtube.com/watch?v=BS6IKdUd2V8




sample of 'code behind' :
JavaScript:
string conn = System.Configuration.ConfigurationManager.ConnectionStrings["testEntities"].ConnectionString;
testEntities x = new testEntities(conn);
var queryRet = (from p in x.customers select p).Take(100);
foreach (var results in queryRet)
{
Console.WriteLine(results.eponimo);
}
James DeMeuse wrote (http://stackoverflow.com/a/28353126) :
I hate to dump on EF because it works so well, but it is just slow. In most cases I just want to find a record or update/insert. Even simple operations like this are slow. I pulled back 1100 records from a table into a List and that operation took 6 seconds with EF. For me this is too long, even saving takes too long.
I ended up making my own ORM. I pulled the same 1100 records from a database and my ORM took 2 seconds, much faster than EF. Everything with my ORM is almost instant.
https://github.com/jdemeuse1204/OR-M-Data-Entities
http://ormdataentities.com/