Contents
Code-based sandbox solutions are also deprecated in SharePoint 2013 and in SharePoint 2016. Sandbox solutions are customization packages that can be used to deploy customizations to SharePoint on the site collection level.
Important: When you use the SharePoint Sandbox Solution scanner, the scan output lists which solutions have an empty assembly, and the tool creates updated sandbox solution packages for you in which the assembly is dropped. You can then simply replace the existing sandbox solution with the updated one.
How to deactivate the linked sandbox solution?
Deactivate the linked sandbox solution at Site Settings > Solutions. Confirm that the form works as expected. Delete the sandbox solution. If you no longer have access to the InfoPath XSN file and source code, you can still fix these forms by deactivating the sandbox solutions that have useless code.
How to tell if SharePoint sandbox solution scanner has useless code?
The SharePoint Sandbox Solution scanner tells you if your InfoPath form has useless code. However, you might wonder how you can distinguish between useless and necessary code-behind because you can only fix useless code. If you still have the original form (not the one you downloaded in previous steps), you can simply look at the code.
Once you have been able to successfully open the existing Visual Studio 2010-based project in Visual Studio 2012, and have handled the items above, simply compiling/building the solution in Visual Studio 2012 should present you with a list of warnings/errors to deal with…
How are custom sandbox solutions generated in Visual Studio?
Design package – Generated by using Design Manager from the publishing site. Custom sandbox solutions – Created in Visual Studio, for example, for branding assets, and do not contain assemblies. Code-based sandbox solutions can be further divided into the following types based on their use cases: