In the last 30 mins of the first of six video tutorials on the SharePoint App Model published on Microsoft’s Virtual Academy, Steve Walker and Vesa Juvonen use some of the techniques likely to be familiar to anyone involved in an effort to persuade people to adopt a new method of computing. The title of this video is Transform SharePoint Customizations to SharePoint App Model: (01) Introduction to App Model Transition Tasks.
The experience of this tutorial as an effort to persuade an audience to do something differently, is exemplified by the frequency of repetition of several recommended approaches. The most popular of these recommendations is a call for SharePoint developers to approach the task of transforming full trust solutions into systems conforming to the new Office (SharePoint) App Model from a functional (rather than technical) perspective. Once the task of renovating code is approached from this perspective, Walker and Juvonen argue, then the steps required to actually effect the intended transformation should no longer be tightly coupled to specific components for the solution. At numerous points over the final section of this first tutorial of the set Walker points to “timer jobs” as, potentially, a non-essential piece of a solution, at least when they are regarded from a functional perspective.
But is a functional approach, complete with the understanding Walker and Juvonen recommend their audience gain of the business requirements, actually a better task for an audience of business analysts, or, perhaps, project managers? Perhaps this is the case. So analysts and their project management counterparts may also want to watch at least this first video tutorial of the set.
The last 10 mins of the video addresses the needs organizations committed to the full trust solution approach to SharePoint customization require to better approach the task. The content in this final segment is all about best practices and is presented by Vesa Juvonen. Presumably the audience should adopt these new approaches to ensure some of the “evergreen” experience of Office 365 feature repair and enhancement (which Walker and Juvonen mention at numerous points in the video) can spill over, effectively, to the SharePoint on-premises community of users. After all, an evergreen experience is certainly required if, for no other reason than to ensure bug fixes, patches and other important changes to server features can be implemented as soon as possible.
©2015, Ira Michael Blonder & Rehmani Consulting, Inc. All Rights Reserved