New Posts New Posts RSS Feed: If LINQ is dying....
  FAQ FAQ  Forum Search   Calendar   Register Register  Login Login

If LINQ is dying....

 Post Reply Post Reply
davidklitzke View Drop Down

Joined: 14-Jun-2007
Posts: 715
Post Options Post Options   Quote davidklitzke Quote  Post ReplyReply Direct Link To This Post Topic: If LINQ is dying....
    Posted: 10-Dec-2008 at 8:51am
A customer or prospect had previously posted:
In Ward Bell's white paper (, he mentioned "Microsoft recently merged announced that L2S is a dead end", is that going to affect DevForce EF?

We are going to begin a new project with DevForce EF, should LINQ be avoided?


The poster subsequently withdrew her post, but the question is a good one, so we decided to answer the question anyway.  Here is Ward's answer.

L2S (LINQ to SQL) is the dead end. LINQ for Entities, aka Entity Framework, is the winner and future direction for MS and the foundation for DevForce EF.  

How does it affect us? POSITIVELY. Because people will become less confused about which Microsoft technology L2S or EF     is good for them; it will become more obvious that they should choose EF and when they choose EF they will be open to the benefits of our DevForce EF product.

LINQ Language Integrated Query is a language feature of  .NET itself.  LINQ describes a general purpose query facility. It is up to developers (both inside Microsoft and outside Microsoft) to provide implementations of LINQ that fit a particular purpose. Thus, there are many LINQ implementations including LINQ for OBJECTS, LINQ for XML, LINQ for ENTITIES, and LINQ for DEVFORCE (my coinage). You can write your own LINQ implementation to query something important to you such as a flat file or perhaps an Excel spreadsheet. Let your imagination lead you! 

 LINQ is not limited to database queries. You should embrace LINQ no matter what data access technology you choose.


Back to Top
 Post Reply Post Reply

Forum Jump Forum Permissions View Drop Down