This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 45%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPV%3C/text%3E%3C/svg%3E)
Hi All,
We are using Sharepoint 2013 on-prem. We have couple of projects/wsps developed in sandbox solutions. Now we require this project in shrepoint 2019 on-premise with content db upgrade solution. Does Sharepoint 2019 on-premise supports sandbox solutions or entire sandbox solutions need to be rewritten with spfx/hosted app etc...? I know for Sharepoint online we have to rewrite but not sure for Sharepoint 2019 on premise. Can you please suggest what can be done?
Thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 96%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Yes, It is possible. You can easily open the sandbox solutions projects in sharepoin 2019 on-premise. As recently we have shifted all the document of Breedium from sandbox solution to sharepoin on premise. If you are facing any type of the issue. So kindly convert your document online from sandbox solution to sharepoint then it will be open in sharepoint 2019 on-premise.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(252.8, 5%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Hi @PRASHANT VYAS ,
Per my research, Code-Based Sandbox Solutions were deprecated in SharePoint Server 2019. As a workaround, we will recommend you to use add-ins as an alternative. Please refer to the document What's deprecated or removed from SharePoint Server 2019. Here is the discussion about the similar issue
https://sharepoint.stackexchange.com/questions/288787/sharepoint-2019-solutions-with-sandboxed-code-are-disabled
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks @RaytheonXie_MSFT . In removed list section, Microsoft has mentioned code-based sandbox solutions were deprecated in SharePoint Server 2013 and have now been removed in SharePoint in Microsoft 365. After careful consideration, we've decided to also remove support for code-based sandbox solutions in SharePoint Server 2019.
so what is mean by removing support? Should I still use sandbox solution in Sharepoint 2019 on-premise?
Hi @PRASHANT VYAS ,
Sandbox solutions actually were not removed in SharePoint 2013, and they were not removed in SharePoint 2016. SharePoint 2019 is the first version where sandbox solutions (.WSP packages) that contain any DLLs get blocked. So we are unable to use sandbox solution in Sharepoint 2019 on-premise
Thanks @RaytheonXie_MSFT . Does it mean even in SP online and SP 2019 on-premise Sandbox solutions containing dll will not work? I have two solutions which deployes CSS/JS to style library and some webparts developed in angular/typescript wih CSOM both contains wsp (dll). Do we need to rewrite using SPFX solutions if we do not want to explore App models/add-ins?
Yes, it means that sandbox solutions that contain assemblies (DLLs) will not work in SharePoint 2019 or SharePoint Online. You can still use sandbox solutions in these environments if they do not include any manage code (i.e. C# or VB). For example, a sandbox solution that provisions a content type and a list using the Feature framework is fine; a sandbox solution that provisions CSS and JavaScript to a document library using the Feature framework is also fine; however, a sandbox solution that includes a visual web part and/or an event receiver is not.
Even when your sandbox solution does not include any managed code, Visual Studio will still include a DLL in the solution package by default. You need to change the Include Assembly In Package project property to tell Visual Studio not to do this. For more information, please see Remove the assembly reference from your Sandbox solution created in Visual Studio.
Thanks a lot @Rob Windsor & @RaytheonXie_MSFT