concept Entity Framework in category asp.net

This is an excerpt from Manning's book ASP.NET 4.0 in Practice.
As we’ve previously noted, the runtime contains all the technologies inside the framework. You’ll get out-of-the-box support not only for ASP.NET, but also for Windows Communication Foundation (WCF), which is the technology used to implement service-oriented scenarios, the Entity Framework (an Object-Relational Mapping [ORM] specifically built for .NET Framework), and so on.
You’ve learned what problems an ORM addresses and why it can ease your mind when you’re developing data access. Now let’s see how to use it. In the coming sections, we’ll use Entity Framework, which is the ORM introduced by Microsoft in the .NET Framework 3.5 SP1. Entity Framework is now in its second version (named 4.0 only because its versioning has been aligned with that of the .NET Framework).
Querying a database using the classic ADO.NET approach requires you to write SQL code and leverage several classes to execute it and read returned data. Querying with Entity Framework is different. Because you don’t work directly with the database, the only structure you need to know about is the model. That’s how the model becomes your database and why your queries are written against it. The burden of translating everything into SQL and executing it against the database is shifted to Entity Framework.
Entity Framework is a huge step towards development simplicity. Remember that in section 2.2.1, we discussed that the classes in the model can be different from the database tables that classes are mapped to. Classes have inheritance. The number of classes and tables does not have to match, and so on. You don’t have to worry about any of these problems. You write queries against the model, and then Entity Framework generates SQL for you. What’s more, classes express business better than database tables do, so writing queries against them is a more business oriented approach.