SharePoint 2010 introduced the client-side object model (CSOM) to allow developers to write applications which interact with SharePoint from client-side code. In SharePoint 2013, Microsoft steps things up a notch by allowing developers to use Representational State Transfer (REST) in conjunction with the Open Data (OData) protocol to perform Create/Read/Update/Delete (CRUD) operations against SharePoint sites and lists for nearly every API in the CSOM. Through the magic of CloudShare web access, we can leverage the CSOM along with REST and OData to interact with our SharePoint 2013 environments from literally anywhere, using any type of client! All code samples in this blog post will be run from my local workstation over 1,000 miles away from my SharePoint 2013 server running in the CloudShare datacenter!
With the recent Release to Manufacturing (RTM) of SharePoint 2013, I figured it was time to see what the new app development model is all about.
Spinning up the farm
CloudShare’s very own Chris Riley recently shared an environment of mine in a blog post about network orchestration. This environment leverages some exciting new capabilities in SharePoint 2010: namely Claims Authentication in a SharePoint 2010 web application and the ability to configure multiple authentication providers in a single zone.