SharePoint 2010 Client Object Model Part 1

InfoPath alternatives for form designing SharePoint

In this article we will discuss about SharePoint 2010 Client Object Model Part 1. Also you can check out my previous posts on:

– Change webpart Title using SharePoint Client object model

– SPContext class in SharePoint 2010

– Switch from Classic to Claims Authentication in SharePoint 2010

Last week one of my colleague took a session for all of us to explain the Client Object Model in SharePoint 2010, so i thought to share the knowledge via this blog article.

What is Client Object Model (COM):
Client Object Model (Client OM) is a unified model which can be used by developers to access the server. The Client OM can be accessed via web services, via a client (JavaScript) API, and via REST. Microsoft SharePoint 2010 introduces three new client APIs that allow you to interact with SharePoint sites from script that executes in the browser, from code that executes in a .NET managed application, or from code that executes in a Microsoft Silverlight 2.0 application.

Key Points one should know about the COM:
There are limitations to what can be done client side compared to server side, say for example you cannot access the FARM level properties, you can get/set only the properties at the web application level.

We cannot elevate the privilege in COM as we can do in server object model.

No SharePoint installation is required in the development machine.Only the Client DLL’s are required.

No Compilation required as required on the server side, NO IISRESET required.

Path to get DLL’s: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI
You can read more about this article over here.

Similar SharePoint 2013 Tutorials


Leave a Reply