5. CSOM in SharePoint 2010
Issues with CSOM
• No Direct Access to
client.svc Web Service
• Must use a Proxy or
Supported End Points
• Supports .NET Silverlight
& JavaScript
Managed OM – Is Easy
Silverlight OM? – Is Easy
JavaScript OM? – Is Not
Easy
9. Changes in SharePoint 2013
Client.svc with REST Clients
• Direct Access to client.svc Web Service
• Access HTTP GET, PUT, Merge, POST
Requests
• OData Implementation
• Writing Code from NON Microsoft Apps
• New APIs for Server Functionality
• API for Windows Phone Development
For More Information
http://tinyurl.com/SP2013Odata
10. New CSOM API Support
E-Discovery
TaxonomySearch
WorkflowSharing
User
Profiles
Analytics
PublishingFeeds
IRM
Business
Data
Lists
Support both Server Side code and REST
12. Changes in SharePoint 2013 CSOM
• Microsoft.SharePoint.Client.dll and Microsoft.SharePoint.Client.RunTime.dll
• Available in SharePoint Foundation
• contains the core classes
16. What’s REST and Why?
Simple and Easier to
Use
• Easier than SOAP Based
WS’s
• Higher Productivity using
JavaScript and JQuery
• Results as JSON and
ATOM
• Everything is URL
• Results can be cached on
Proxy Servers.
18. REST in SharePoint 2013
Replace
• http://intranet/_vti_bin/client.svc/web
with
• http://intranet/_api/web/
• Lot more simple URL
• Helps in 256 Character Limit of URLs
in browser
• ListData.svc is still there for
backword compatiability
• OLD Aps will still work but needs to
be updated
21. OData Terms and Concepts
OData Described in Entity Data Model by
Collection
Entity Set
A Navigation Property on an entity type that identifies a collection of
entities
Entry
Entry type
Note: May be Part of a type Hierarchy
Property of an Entry Primitive or complex Entity type property
Complex Type Complex Type
Link A Navigation Property defined on an entity type
Service Operation Function Import
22. Methods will be mapped into eitherOData Maps CRUD Operations to HTTP Verbs
OData Implementation Details
More Information @ http://www.odata.org/