Home » SharePoint 2013 » With SharePoint 2013, Microsoft Introduces a New Application Model

With SharePoint 2013, Microsoft Introduces a New Application Model

As Steve Fox makes clear in a video tutorial titled WELCOME TO THE NEW SHAREPOINT 2013 APPLICATION MODEL, developers will need to choose new sets of tools and approaches to work with the new application model Microsoft has built for SharePoint Server 2013.

Steve Fox, Director of Services at Microsoft® brings to this video tutorial, and, indeed this entire set of tutorials on application development for SharePoint Server 2013, a deep level of experience with the topic. He is also one of a team of three authors who produced a new technical publication, “Beginning SharePoint 2013 Development”, which is published by Wrox.

Microsoft has provided three different server architecture options for SharePoint Server 2013. These include

  1. SharePoint Hosted
  2. Autohosted
  3. and Provider-Hosted

As Steve Fox explains, No server side code is allowed in a SharePoint Hosted implementation architecture. So all applications must be “made up of static files that reside directly in your instance of SharePoint”.

The “Autohosted” option is built on Windows® Azure®. The server is, once again, inaccessible within this architecture. The development approach, for this option, is to create an “[a]pp that is designed to be deployed to Azure, so it is hosted outside of SharePoint, and can run custom code.”

The final option, “Provider-Hosted” provides the widest range of options for SharePoint development. Developers work to build an “[a]pp where the files for the application exist on an external server . . . In this model, SharePoint is really just redirecting users to a web page, so you can use any operating system and application server you want as long as it can fulfill web requests. You could be PHP developer with a Linux machine and still make SharePoint apps.”

The consistent theme across all of these methods is a SharePoint Server isolated from any/all processes built to equip users to better exploit the servers features and capabilities.

The static applications Steve has referred to are usually built with a scripting language, JavaScript, for example. The jQuery function library, for example, can be used to add processing capabilities to custom scripts.

Ira Michael Blonder

© Rehmani Consulting, Inc. & Ira Michael Blonder, 2013 All Rights Reserved