Client Object Model Part -1

Here I am starting a series of posts on Client Object model.

Sharepoint 2010 has introduced three types of COM (Client Object Model )

1)   Managed Client Object Model -Implemented in .NET CLR

2)  ECMA script

3)  Silverlight Client object model.

Client APIs allows you to interact with SharePoint sites from script that executes in the browser i.e. it is not mandatory to install Sharepoint on the client machine where application is being run and it can communicate with Sharepoint server remotely.

 .NET managed, and Silverlight client object models provides a subset of the server object model that is defined in Microsoft.SharePoint.dll, including objects that correspond to major objects at the site-collection level or lower in the SharePoint Foundation hierarchy.

The great advantage of it is that syntax is like the SharePoint Object Model.

Syntax of two types of object model when compared looks like this.

Server side syntax	Client side syntax
SPContext	ClientContext
SPSite	Site
SPWeb	Web
SPList	List

Now to implement the client object model in the solution we need to refer  the dlls required for each type of Cilent object model.

1)      Managed Client Object Model:

Dlls required -

a)  Microsoft.SharePoint.Client.dll,

b)   Microsoft.SharePoint.Client.Runtime.dll.

Location : 14/ISAPI folder.  Usually, the location would be at "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI".

b)      Microsoft.SharePoint.Client.Silverlight.Runtime.dll.

Location  :  "C:\Program Files\Common Files\Microsoft Shared\Web Server\Extensions\14\Template\LAYOUTS\ClientBin

So from the next post will start some samples of implementation of three types of client object model.

Continue reading Part -2 .