What is and why use Sandbox Solution?
Microsoft had introduced SharePoint Sandbox Solutions for the first time in SharePoint 2010. Sandbox solutions enabled site collection users to upload their own custom solutions.
For those who do not have SharePoint Farm privileges, this solution proved to be very useful. All the user had to do was create/develop a Sandbox solution using Visual Studio, upload it to the solution gallery of the particular site collection and it was ready to use after activation.
Types of Sandbox solutions
Sandbox solutions are of two types namely code based and declarative (or NCSS) solutions.
Code based Sandbox Solutions
Code based Sandbox solutions are fully declarative solutions which contains server side code consisting of .net assembly file. This is the feature that Microsoft has recently deprecated.
Declarative Sandbox Solutions or NCSS
Declarative Sandbox solutions on the other hand, are those which have only HTML markup and JavaScript code. These are also known as No-Code Sandboxed Solutions (NCSS).
Announcement from Microsoft
Microsoft first announced the deprecation of code based sandbox solutions back in January 14, 2014. On July 29, 2016 they announced that they would completely remove code-based sandbox solutions by the end of the next month.
Ideally a sandbox solution is used to create workflows and web parts, feature receivers, list receivers. They are custom-coded and are hosted on the server-side. Deprecating code based sandbox solutions would prevent the following from working:
Event receivers
Feature receivers
Coded workflows would cease to work
Coded InfoPath would be rendered non-functional
Web parts created under Sandbox solutions
Click Here to Get 3 Days of Sharepoint Consulting FREE
Will Sandbox solutions be entirely disabled? How can we save our solutions?
Both types of Sandbox solutions are disabled if they have a .NET assembly file (.dll). By default, solutions created in Visual Studio 2015 and Visual Studio 2013 using Sandbox template create an assembly (.dll) files. However, for a fully declarative solution you will need to disable assembly from your solution.
Whereas the Code based solution is entirely disabled making it important to ensure you have a backup plan that can achieve similar functionality to replace them. The following methods can help you overcome the setback:
Use a JavaScript Object Model (JSOM) or SharePoint REST/ OData service calls.
Use a SharePoint Add-In Model (SharePoint Hosted, Provider Hosted) and Remote Event Receivers.
In short, all sandbox solutions will have to be migrated to No-code Sandbox Solution (NCSS).
How do you manage the situation? – Here’s what we can do for you.
We have been working on SharePoint for long and our developers make it a point to keep themselves up-to-date with the latest changes and features in both SharePoint and Office 365. We have already helped our existing clients to migrate from custom-code sandbox to no code base sandbox solution to overcome the deprecation issue.
Here’s how we conduct the transition.
We identify the sandbox solutions that have been deployed in your site collections by downloading it for each site collection and checking the archives using PowerShell.
We replace code based sandbox solution with JavaScript object models and/or creating SharePoint Add-ins (i.e. SharePoint Apps)
How our SharePoint consultants can help you?
If you haven’t migrated to cloud-based solutions yet or want to enquire about anything related to SharePoint, get in touch with us and we’ll help you out.
We have the best SharePoint experts in our team, who can understand your existing solution quickly and start working with minimum guidance on a solution for you.
