I create sandbox webpart in on-premise server and I want to upload in SP online.

When i trying to activate a solution, this is following error:

enter image description here

How to resolve this problem. Thank you previously..

  • Have a look HERE
    – Gintas K
    Commented Nov 29, 2016 at 12:45

2 Answers 2


The sandbox solution has been deprecated based on Sandboxed Solutions Deprecation , and you will need to convert your solution to SharePoint Add-ins, to get started check SharePoint Add-ins and Get started creating provider-hosted SharePoint Add-ins

Meanwhile , the following steps was worked before , Try it

  • Open your solution via visual studio >
  • Right click on your project > Properties >
  • Set Include Assembly In Package to FALSE

enter image description here

  • Rebuild the solution and try again to upload WSP to SharePoint online.
  • Whrere i try to add webpart in my page, web page says: $Resources:core,ImportErrorMessage;
    – Goshky
    Commented Nov 29, 2016 at 13:24
  • are you talk about Include Assembly In Package steps ? , this was work before based on this thread social.technet.microsoft.com/Forums/en-US/… , Commented Nov 29, 2016 at 13:25
  • I activate webpart, but where i want to use error is : $Resources:core,ImportErrorMessage
    – Goshky
    Commented Nov 29, 2016 at 13:27
  • this mean the solution has been activated but , the issue in activating web part ? right ? Commented Nov 29, 2016 at 13:28
  • 1
    what this solution do/have ? meanwhile as I told you above The sandbox solution has been deprecated so this may be not work , can you convert it to add-in ? Commented Nov 29, 2016 at 13:32

Does your solution contain custom code?

If yes , have a look at this Technet Blog

  • Can you please add more details to your answer? If the link breaks it will render useless to future readers Commented Nov 29, 2016 at 13:13
  • of course. @Goshbuy used a custom webpart in his solution, which can contain custom code (C# i guess). Sandbox solution containing custom codes have been deprecated since 2014 and Microsoft decided to disable them since August 2016. Commented Nov 29, 2016 at 13:27
  • So, if the webpart is based on C# code, the solution will never be able to be activated. You need to remake the webpart by using client side languages ( Html / Javascrit ...) Commented Nov 29, 2016 at 13:29
  • You can edit your answer (click the edit button below your answer), and put this information there.
    – wjervis
    Commented Dec 8, 2016 at 11:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.