Skip to content
This repository has been archived by the owner on Mar 11, 2020. It is now read-only.

SharePoint 101 I. Client side dev ~ Choosing your SharePoint App development pattern

Philippe Lavoie edited this page Mar 11, 2020 · 1 revision

SharePoint 2013 pushes developers hard in the direction of "not-on-the-server". Microsoft introduced the new SharePoint App model, which greatly increases the isolation of SharePoint custom components by forcing them to run from the client-side.

App Development and Hosting Patterns

  • The whole idea to is abandon the farm solution, full-trust model in order to gain stability for critical SharePoint infrastructure. For any new custom functionality, the idea is to build it as sandboxed as possible in an App with permissions set as low as you can crank them down. Do one thing, do it right, and use SharePoint as a simple backend database.
  • The two different models:
    • SharePoint hosted, the simplest model
    • Provider hosted, where your app can run on any server with a technology of your choosing
  • Two discontinued models:
    • Sandbox solutions never took off; running (sandboxed as it was) code on the server with them has become deprecated; they got re-branded as No-Code Sandboxed Solution
    • Auto-hosted apps are a thing of the past, RIP

References:

App Development Prerequisites

Tutorial: Creating your first SharePoint hosted app

Reference:

Clone this wiki locally