SANDBOX SOLUTIONS NO CODEMicrosoft – Iselin, NJ

August 24, 2016

TOPICS

• What are Sandboxed Solutions• Microsoft Announcements

• Original Announcement – January 14, 2014• Recent Announcement – July 29, 2016

• Customer Impact• Next Steps• Scenarios

WHAT ARE SANDBOXED SOLUTIONS?

SANDBOXED SOLUTIONS

• Sandboxed solutions are packaged as SharePoint solution package (WSP) files that contain assemblies, other non-compiled components, and an XML manifest file

• Sandboxed solutions are executed in a unique application domain. Because the application domain is unique to your solution, SharePoint is able to monitor your solution for performance issues and resource use, and it can terminate your code if it exceeds the boundaries set by the IT team

• Sandboxed solutions have specific limitations over farm solutions such as : No visual web parts, no user controls, no timer jobs, no application pages, no elevated priv.

• https://msdn.microsoft.com/en-us/library/ff798382.aspx

WHO’S USING SANDBOXED SOLUTIONS?

SO WHY DID WE BUILD SANDBOXED SOLUTIONS

1. Sandboxed was the way for SharePoint Online or Office 365 (multi-tenant) 2. It was an easier investment / step to create sandboxed solutions from farm

solutions3. Apps / Add-Ins were not adopted because of the learning curve, special

environmental configurations and lack of trust in the model/technology.

MICROSOFT ANNOUNCEMENTJANUARY 14, 2016

• Microsoft Announces, Deprecation of Custom Code in Sandboxed Solutions• Sandboxed solutions that contain only declarative markup and JavaScript — which

we call no-code sandboxed solutions (NCSS) — is still viable, we have deprecated the use of custom managed code within the sandboxed solution

• The new SharePoint app model as a replacement to those scenarios that required the use of managed code.

• We realize that our customers have made investments in coded sandboxed solutions and we will phase them out responsibly

• In scenarios where you have to develop a farm solution or coded sandboxed solution, we recommend that you design it so that it can easily evolve toward a more loosely coupled development model

MOST RECENT ANNOUNCEMENTJULY 29, 2016

• We started taking steps this week to complete the removal of code-based sandbox solutions as part of the phased approach we announced in 2014 when we deprecated the feature.

• Detailed below are recent actions taken and what to expect next:• As part of the removal process, activation of new code-based sandbox solutions, as

well as updates of existing solutions are no longer available.• In the coming weeks, running code-based sandbox solutions in SharePoint Online

multi-tenant environments also will be disabled. Customers with these solutions should watch the Message Center and Service Health Dashboard (SHD) for details, timelines, and exception processes. 

CLIENT EMAIL WARNINGSPROBLEM – SANDBOX CODE DETECTE

CLIENT EMAIL WARNINGSOK – NO SANDBOX CODE

WHAT DOES THIS MEAN?

• The following items will stop working• Event receivers• Feature receivers• Workflows (coded)• InfoPath forms (if using code behind the forms)• Web parts (if coded using sandbox code)

• You are no longer able to activate or upgrade solutions with server side code• Current solutions need to be rebuilt without server side code• Currently there is no restriction in deploying ‘sandbox solution’ as long as it does not

contain server side code• No Code Sandbox Solutions (NCSS) continue to be supported. (but deprecated)

WHAT CAN WE DO NOW

• Identify • Detect Sandbox Code

• Microsoft PnP - Sandbox solutions inventory script for SharePoint Online

• Resolve• Recompile Code without the DLL

• https://support.microsoft.com/en-us/kb/3183084• Pull the DLL out of the existing WSP

• @BostonMusicDave - Sandbox Solutions removed from SharePoint Online–Here’s the fix for your Visual Studio developed WSPs to get them to activate

• Convert to Apps / Add-ins Model

DEMO