With the new App model coming in SharePoint 2013, the remote client APIs are becoming increasingly important. How do you choose between them, to know when the REST/OData approach is best? How do you find out how best to use it? How do you avoid common pitfalls? How do you handle different remote authentication and access scenarios? In this session, we’ll cover all of these topics and more, ensuring you leave with a solid and deep foundation of both standard and advanced use cases with the SharePoint 2013 REST services.
6. SharePoint 2007 Web Services
1. Alerts 13. Forms Services Web service 27. Search Web service
2. Area Web service 14. Imaging Web service 28. Users and Groups Web service
3. Authentication Web service 15. Lists Web service 29. User Profile Change Web
4. BDC Fields Resolver Web 16. Meetings Web service service
service 17. Official File Web service 30. User Profile Web service
5. BDC Web service 18. People Web service 31. Versions Web service
6. CMS Content Area Toolbox 19. Permissions Web service 32. Views Web service
Info Web service 20. Published Links Web service 33. Web Part Pages Web service
7. Copy Web service 21. Publishing Service Web service 34. Webs Web service
8. List Data Retrieval Web service 22. Search Web service 35. Workflow Web service
9. Document Workspace Web 23. SharePoint Directory
service Management Web service
10. Excel Services Web service 24. Sites Web service
11. Forms Web service 25. Slide Library Web service
12. Forms Services proxy Web 26. Search Crawl Web service
service
31. Key Takeaways
SOAP / CSOM REST
Other options
ASMX, CSOM
Roll-your-own
Going back Know your stack!
CrUD - Digest Payload
Concurrency Limiting calls
Async
32.
33.
34. Advanced Topics
More on Paging
Social Safety
Async in .Net
Batching
Paging & Counting
Relationships in .Net
Editor's Notes
Good resource: http://msdn.microsoft.com/en-us/library/fp142385.aspx
Client-Side OMKinda-like SOM3 Versions.NetJSSilverlightREST/ODataStandards-basedOpen to anyoneWidely known
Demo Reminder Script:Explain ListData.svcvsClient.svcOpen browser to listdata.svcShow lists -> one list -> one list item -> one field (CreatedBy)Show Query - $filter=StartsWith(Title,’[X]’)Show SelectShow OrderByShow Fiddler (JSON - application/json;odata=verbose)Show Client.svc/_vti_bin/client.svc -> /_api_api/web/getAvailableWebTemplates(1033)_api/social.following/my/Followed(types=4)C# Proxy - uses “LINQ TO WCF Data Services”Generating proxyWhere,OrderByJS Example – basic, then more complex
Client-Side OMKinda-like SOM3 Versions.NetJSSilverlightREST/ODataStandards-basedOpen to anyoneWidely known
Good:MUCH larger footprint, ESPECIALLY for REST service More MS Investment? One less “moving part”? New API for WPhoneBad: Not like-for-like (CSOM still does more, like Taxonomy fields) Less “RESTful” no $metadata (for now?) NO LONGER STANDARDS COMPLIANT!