Not all server-side objects are available within the Client Object Model. Generally speaking, all objects from SPSite downward are included. No representations of administrative classes, such as those found in the Microsoft.SharePoint.Administration namespace, are included. The Client Object Model is encapsulated in four namespaces:
Microsoft.SharePoint.Client This namespace contains representations of many commonly used server objects such as SPSite, SPWeb, SPList, SPListItem, and SPField. These objects are implemented in the Client Object Model without the SP prefix—so, for example, SPSite in the Server Object Model maps to Site in the Client Object Model. This is the same for all variants of the Client Object Model. The exception to this rule is the SPContext object, which is represented as Client Context in the Client Object Model. The ClientContext object is a key component in the Client Object Model and exposes functionality that has no direct counterpart in the SPContext server-side object. We’ll cover ClientContext in greater detail in the next section.
Microsoft.SharePoint.Client.Utilities This namespace contains representations of a few commonly used server-side utility classes. Those included are HttpUtility, which maps to SPHttpUtility on the server side; PrincipalInfo, which maps to SPPrincipalInfo on the server side; and Utility, which maps to SPUtility on the server side.
Microsoft.SharePoint.Client.WebParts This namespace contains representations of server-side objects that are commonly used in the management of web parts. Using the classes in this namespace, you can access and modify web parts and web part pages.
Microsoft.Sharepoint.Client.Workflow This namespace contains representations of a number of server-side classes concerned with the operation of workflows. Using the classes in this namespace, you can manage workflow associations and templates.
When writing code that uses the Server Object Model, you generally start with something like this:
Let’s take a look at how to achieve a similar result by using the Silverlight Client Object Model:
The Client Context class includes a few methods that are essential to the workings of the Client Object Model. The first of these methods is the Client Context. Execute Query Async method.
Earlier, in our architecture diagram, we saw that the Client Object Model makes use of a WCF service as a proxy to perform operations on the server. To reduce network load, what actually happens is that all requests are queued by the ClientContext object and are sent to the server only when the Execute Query Async method is called. Conceptually, this is easy to understand, but it makes for some interesting caveats when it comes to developing against the Client Object Model.
To see how this works, consider our earlier Silverlight code sample:
Share Point 2010 Related Interview Questions
|Web Services Interview Questions||XML Interview Questions|
|Share Point 2010 Interview Questions||ASP.NET Interview Questions|
|Share Point Administration Interview Questions||BizTalk Admin Interview Questions|
|Microsoft Office SharePoint Server (MOSS) Interview Questions||Biztalk Server Interview Questions|
|Asp Dot Net Mvc 4 Interview Questions||Biztalk Esb Toolkit Interview Questions|
|InfoPath Interview Questions|
Share Point 2010 Tutorial
The Microsoft Sharepoint 2010 Platform
Developing With Sharepoint 2010
Presentation Layer Overview
Client Object Model
Infopath Forms Services
Enterprise Content Management
User Interface Customization
Application Services Overview
Service Application Framework
Word Automation Services
Data Access Overview
Linq To Sharepoint And Spmetal
Business Connectivity Services
User Profiles And Social Data
Packaging And Deployment Model
All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd
Wisdomjobs.com is one of the best job search sites in India.