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

I was researching about the SharePoint Client Object Model and REST but I am confused which one is strongly typed.

share|improve this question
The Client Object Model is strongly typed. – Vardhaman Deshpande Nov 5 '12 at 9:03
up vote 2 down vote accepted

ASP.Net web services isn't strongly typed.

Most other objects in the other methods of interacting with SharePoint are strongly typed, however there are functions that can return objects that aren't strongly typed, but these link back to web services.

Here is a table that lists the differences for you: Data Access for Client Applications

share|improve this answer
So can I say that both are strongly typed but with some exceptions? – user3470 Nov 5 '12 at 11:22
Yes, the exceptions are shown on the link I provided you. – Hugh Wood Nov 5 '12 at 11:36

Depends on what you mean by strongly typed.

The Client Side Object Model contains a lot of classes for working with the SharePoint objects, and these are strongly types. But the moment you start working with the content of lists, then you have to know or investigate the type of columns at runtime.

The REST interface is all XML/JSON are therefore only strings. But the proxy generated by visual studio creates wrappers around your list/content types which are strongly typed.

So in general I'd recommend using REST for accessing/modifying the content of lists/libraries and CSOM for the rest.

share|improve this answer

Your Answer


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