Email: Password:       Forgot Password 
A Saarsha Group Online Community for dot net codes group like C#, Asp.NET, VB.NET, Sharepoint, JavaScript, JQuery, Ajax, SQL, WCF, WPF.
CAML Vs LINQ in SharePoint 2010

Posted On: 05/11/2014 21:46:48
LINQ to SharePoint List
The code we have written for querying the SharePoint List in LINQ, that was first converted to CAML Query and then that CAML Query access the SharePoint Database and bring back the result.

So LINQ is a front end to CAML so of course CAML is faster.

Disadvantages of CAML:
  • CAML query is text based so, if we are joining two lists across a lookup field there may be various problems associated with that.
  • There is no mechanism to know until run time if the query is written correctly or not. If the query is not correct, then it will simply fail at run time. Means it won't support at design time.
  • When writing the query, you have no idea what CAML elements are legal in the syntax without having a reference open.
  • The query is somewhat difficult to understand. We cannot determine easily what the query is doing and what lists are being joined.
  • The data returned from the query is placed in a SPListItem collection, which does not provide strongly typed business entities.

Advantages of LINQ over CAML:
  • First advantage is, it is an object-oriented query language.
  • It can provide strongly typed objects at design time; we can create queries in code and can check that they are correct because we can the compiles the code.
  • The results are returned from queries are strongly typed objects, so the items and fields can provide compile-time checking.

    Disadvantages of Using LINQ
    LINQ translates the LINQ queries into Collaborative Application Markup Language (CAML) queries thus adding an extra step for retrieving the items.a
         HOME   |   Submit Article   |   Contact Us   |   About Us   |   Terms & Condition   |   Advertise With us