views:

64

answers:

4

There are so many terms and it is getting hard to learn the thing you are after because of the noise.

Is Linq to Entities just the practice of using Linq queries against the entities generated by the ADO.NET Entity Framework? Or, is it a separate technology?

If it isn't a separate technology, why does it have another confusing name as though it were?

+5  A: 

LINQ to entities is a LINQ provider for entity framework model.

The thing that analyzes lambdas, part of entity framework.


To understand nature of LINQ thoroughly, i recommend book "Pro LINQ".

Arnis L.
Thanks much. Which really means, to a developer using it, it provides a meant to write linq queries to query the entities generated by the Entity Framework. And I do understand what you're saying. That it is actually this set of classes that implement IQueryable and that build expression trees and save every linq query into an expression in the expression tree, then when someone fires off the iterator on the query to execute it, it translates that into a SQL query.
Water Cooler v2
+1  A: 

Linq to Entities is indeed practice to user Linq to query ADO.NET Entity framework. But under the hood there is some separate technology (provider) which converts expression tree built by linq to database query.

Ladislav Mrnka
Thanks. I do understand what you're saying. Thanks for the clarification.
Water Cooler v2
About 5 more minutes before I can mark this answer as the best. :-)
Water Cooler v2
+4  A: 

Is Linq to Entities just the practice of using Linq queries against the entities generated by the ADO.NET Entity Framework?

Yes. :)

Liggi
Many thanks. Someone marked you down, but I think your answer helped just as much as any other. In fact, it was the most precise and most practical.
Water Cooler v2
Haters gonn' hate. ;).
Liggi
+2  A: 

"LINQ" is a getting to be a rough term because people use it imprecisely in so many contexts.

A lot of people I've run into, when they say, "Linq" mean "LINQ to SQL".

LINQ really is a standard query system that integrated into the language which can fit on top of many different sources of data.

  • LINQ to Objects -> Using Linq to query objects in memory
  • LINQ to XML -> Using Linq to query XML documents
  • LINQ to Entities -> Using Linq to query the entities generated by the ADO.NET Entity Framework
  • LINQ to SQL -> Using Linq to query SQL Server tables (pretty much obsolete after Entity Framework 4.0)
  • LINQ to [Your favorite API] -> Linq can be used to query all sorts of data sources. We're seeing it used for SharePoint and MS CRM these days, but it's being used more and more against all sorts of stuff.
Dave Markle
Thanks, Dave. I do understand what Linq is. It is a mechanism for creating and using a data pipeline and then to transform or query or project data using that pipeline from a data source, regardless of what the nature of the data source is (as long as it is IQueryable).
Water Cooler v2