SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In the past I tried with linq using spmetal, but after the project was almost finished I realized of some limitations, this tool does not generate fields for creation date, modified date, also it doesnt work for lookup columns. So at the end I ended with a combination of LINQ to Sharepoint and also CAML.

From the development point of view which is the best way? Specially if I need to access by code special columns like images, lookup fields, metadata service fields, users, creation date, etc.


share|improve this question
up vote 2 down vote accepted

linq to sharepoint -in my opinion- is great, but yes it does have some limitations. From a development point of view I try to use it as much as possible knowing it's fairly new and will get even better. This article may help you decide whether to use it in your situation.

good luck.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.