SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

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

If do some client programmering, what factors should I take it into consideration if I gonnna use javascript/ECMAScript or .net in relation to retrieve some functionality from SharePoint and apply it to my client webpage?

enter image description here

share|improve this question

closed as too broad by Robert Lindgren, Eric Alexander, RJ Cuthbertson, John Chapman, Jesus Shelby Jul 29 '13 at 19:45

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 0 down vote accepted

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:

• Microsoft.SharePoint.Client.dll

• Microsoft.SharePoint.Client.Runtime.dll

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:

• Microsoft.SharePoint.Client.Silverlight.dll

• Microsoft.SharePoint.Client.Silverlight.Runtime.dll

These files are usually installed into this directory: %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS\ClientBin

ECMAScript Client Object Model The JavaScript client object model consists of several JS files that are all installed into the LAYOUTS folder under the path %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS:

• 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

share|improve this answer
Possible to use LINQ to SharePoint for a client? – HelloWorld Jul 25 '13 at 10:28
Yes, refer to this site for implementation.… – Pushpendra Jul 25 '13 at 10:33
If I create a MVC page and what is the appropriate to use that is ECMA/JavaScript or .net client code? – HelloWorld Jul 25 '13 at 10:40
Ideally speaking SP2010 object model doesn't support MVC framework. You should go for ECMA/Javascript. Pls refer this link… however you can go for SharePoint WebServices from your ASP.NET MVC app. – Pushpendra Jul 25 '13 at 11:06
is it same for SharePoint 2013? – HelloWorld Jul 25 '13 at 12:29

Pls have a look at this Question on this site regarding more about MVC.

share|improve this answer

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