Home » sharepoint » SharePoint 2013 » Understanding the Implications of Implementing Full Trust Solutions for SharePoint

Understanding the Implications of Implementing Full Trust Solutions for SharePoint

SharePoint-Videos.com has published a series of video tutorial sets on the development options available to organizations implementing SharePoint Server 2013. One of these sets, SharePoint 2013: Beginning Development, which is authored by Steve Fox, a Director at Microsoft®, provides administrators, developers, architects and business analysts with an overview of the range of development options before them when they consider how best to implement new features for this computing platform.

What is NOT included in this tutorial set is a presentation of why the new Cloud App Model, and the common reliance, by any of the current development methods, on relatively tame JavaScript coding methods, makes sense from a support and security standpoint. This gap is filled quite nicely by a video presentation produced by Microsoft and offered on MSDN.

One of the speakers in this video presentation is Mr. Keenan Newton, who serves as a Senior Product Manager for Microsoft. Mr. Keenan ” . . . focuses on the SharePoint developer audience”. The video presentation is titled 0 to 60: Developing Apps for Microsoft SharePoint 2013. In this presentation Mr. Newton comments on the early stage development model for building custom applications for SharePoint: ” . . . because you could write this code [meaning SharePoint solutions], which ran in the same application domain as SharePoint, you could effect the behavior of SharePoint. Now, within the full trust solution that you wrote that might be perfectly acceptable; however, in most SharePoint environments, you have multiple solutions. So if we have two solutions that are trying, let’s say, to effect the behavior of search, you’ll probably run into problems, because you might buy one third party application and expect search to run one way, and then you create a custom solution, thinking that it will run a slightly different way, and all of a sudden you are going to start seeing errors, unexpected behavior within your environment. There’s no isolation between solutions. It’s all running within the same app domain.”

Mr. Newton then makes an important claim about the reasons Microsoft customers avail of the services of Premier Field Engineers (PFEs): ” . . . 99% of all SharePoint help desk calls come from customizations”.

If, for no other reason than to mitigate the risk of a costly, and very dangerous support headache, SharePoint 2013 stakeholders should at least investigate the new Cloud App model. This method will provide them with a safer approach to customizing end user experience of the SharePoint 2013 computing platform. At the same time, SharePoint Server 2013, itself, will be insulated from any/all of the custom processes developed for the platform.

In the next post to this blog I’ll wrap up my comments on this very informative video presentation. Please contact us if you would like to discuss your organizations needs for SharePoint 2013 customization.

Ira Michael Blonder

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