SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It only takes a minute to sign up.Sign up to join this community
Difference between Client Object Model and Server Object Model in SharePoint 2010
Server Object Model:
1-SharePoint itself uses the server object model.You can also use this model on a sharepoint server bcz it has some dependencies satisfied by the sharepoint server.
2-Here you can use LINQ programming like LINQ to SharePoint.
3-different classes are there like SPFarm, SPServer, SPService, and SPWebApplication etc.
Client Object Model:
Client object model brings a major portion of that rich server-side functionality as a Client-side API, which can be used in a .NET client such as a WPF application, in a Silverlight application, or in a simple client such as ECMAScript. As Silverlight runs on the client rather than running server - side, the client Object Model (COM) makes it easier for developers to build rich Silverlight applications on SharePoint. The addition of Silverlight integration to SharePoint, a client object model is critical because it makes it easier for developers to write applications against a full object model, rather than trying to call web services from within their client applications.
.NET Client Object Model To develop a .Net Managed application, reference two DLLs:
These files are usually installed into this directory: %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\ISAPI
Silverlight Client Object Model To develop a Silverlight application, use the following two assemblies:
These files are usually installed into this directory: %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS\ClientBin
• SP.js/SP.debug.js • SP.Core.js/SP.Core.debug.js • SP.Runtime.js/SP.Runtime.debug.js • SP.Ribbon.js/SP.Ribbon.debug.js • JsGrid.js/JsGrid.debug.js • JSGrid.Gantt.js/JSGrid.Gantt.debug.js
Pls have a look at this Question on this site regarding more about MVC.