After LINQ got introduced, many developers moved to LINQ. There are some blogs which mentions that if performance is your major requirement, then CAML is still the preferred way.
And now SharePoint 2013… What is your take on future of CAML?
Please share your thoughts.
(Visited 21 times, 1 visits today)
To further what Sreeharsha said, yes CAML is the same in 2010 as it is in 2013.
The problem with using LINQ is that the CAML statements aren’t optimised, the actual transformation betwen LINQ and CAML is very quick less than 0.1ms, however the statements aren’t always perfect. I would log the CAML query and use that after designing your LINQ or do as I have done and make your own wrapper for CAML which doesn’t have the issues like bad joins etc yourself.
(Visited 1 times, 1 visits today)
