2. MySelf
User Group Leader of SharePoint Techies,
http://www.facebook.com/pages/SharePoint-
Techies
Working independently on SharePoint
technologies.
Trainer for Microsoft Office SharePoint Server
2007 and Window SharePoint Services 3.0 at
AUC Technologies.
3. Agenda
This Session is divided into two
Client Side Object Model
NET Client OM
ECMAScript Client OM
Silver Light API
Questions
4. Why Client Object Model?
More SharePoint Web services
is a major request
Client Object Model provides complete API instead
of more services
Provides an abstraction layer to return results as
recognizable SharePoint objects
Consistent developer experience across platforms
(.NET, ECMAScript, Silverlight)
5. Equivalent Objects
Server .NET Managed Silverlight ECMAScript
(Microsoft (Microsoft.SharePoint (Microsoft.SharePoint (SP.js)
.SharePoint) .Client) .Client.Silverlight)
SPContext ClientContext ClientContext ClientContext
SPSite Site Site Site
SPWeb Web Web Web
SPList List List List
SPListItem ListItem ListItem ListItem
SPField Field Field Field
6. Using the Client Object Model
ECMAScriptControls and Logic
Browser
JSON Response
ECMAScript OM Server
XML Request
OM
Proxy
Client.svc
XML Request
Proxy
JSON Response Content
Managed OM
database
Managed Client
Managed Controls and Logic SharePoint Server
10. ECMAScript Client OM
ECMAScript Client OM is easily added to a
SharePoint ASPX page - reference:
_layouts/sp.js
Add this using <SharePoint:ScriptLink>
All libraries crunched for performance
Use un-crunched *.debug.js by adding
<SharePoint:ScriptLink … ScriptMode=“Debug” />
Method signatures can be different
Different data value types