SharePoint 2013 Best Practices: What client API should you choose when building Apps?

SharePoint 2013 Best Practices: What client API should you choose when building Apps?

There are a lot of different options when it comes to communicating with SharePoint. Here's som advice when to use them when building Apps:

  • Apps that offers Create/Read/Update/Delete (CRUD) actions against SharePoint or BCS ( Business Connectivity Services ) external data, and are hosted on an application server separated by a firewall benefit most from using the JavaScript client object model.
  • Server-side code in Apps that offer Create/Read/Update/Delete (CRUD) actions against SharePoint or BCS external data, and are hosted on an application server but not separated by a firewall mainly benefit from using the .managed client object model, but the Silverlight client object model, JavaScript client object model or REST are also options.
  • Apps hosted on non-Microsoft technology (such as members of the LAMP stack) will need to use REST.
  • Windows phone apps need to use the mobile client object model.
  • If an App contains a Silverlight application, it should use the Silverlight client object model.
  • Office Apps that also work with SharePoint need to use the JavaScript client object model.

 

See http://msdn.microsoft.com/en-us/library/jj164060(v=office.15).aspx for more general guidelines concerning client API choices and solution development.

See http://social.technet.microsoft.com/wiki/contents/articles/12438.sharepoint-2013-best-practices.aspx for an overview of SharePoint 2013 Best Practices

Leave a Comment
  • Please add 6 and 4 and type the answer here:
  • Post
Wiki - Revision Comment List(Revision Comment)
Comments
Page 1 of 1 (3 items)
Wikis - Comment List
Posting comments is temporarily disabled until 10:00am PST on Saturday, December 14th. Thank you for your patience.
Comments
Page 1 of 1 (3 items)