none
Is Sandbox solution replaced by SharePoint Apps in SharePoint 2013 Preview RRS feed

  • Question

  • Hi,

    I am curious to know, if the apps for SharePoint is the replacement of Sandboxed solution ? The MicroSoft has recommended the new app model over the Sandboxed solution.

    Can some one explains me, which is more flexible and why ?

    Thanks in Advance


    Please remember to click "Mark As Answer" if a post solves your problem or "Vote As Helpful" if it was useful. It'll help other users who are visiting your thread for the similar problem.


    • Edited by Arun Kumar Arora Monday, July 30, 2012 4:45 AM
    • Moved by Aviw_Moderator Monday, September 24, 2012 5:14 PM Apps (From:SharePoint 2013 Preview for Developers)
    Monday, July 30, 2012 4:18 AM

Answers

  • One other thing to note about sandbox solutions is that Microsoft is deprecating them in SharePoint 2013. This means that the functionality will still be available for use in SharePoint 2013, but primarily for backwards compatibility with existing solutions built using the sandbox solution approach. Microsoft's guidance is that if you are building new applications that in the past you would have deployed as sandbox solutions, you should use the new App model for those solutions instead of using sandbox solutions. They took a similar approach in SharePoint 2010 with the STSADM command line administration tool when it was deprecated in favor of the SharePoint 2010 Management Shell and the numerous PowerShell cmdlets deployed with that tool. STSADM is still available in SharePoint 2010, but mainly just to allow for older scripts and tools that use STSADM to still function with SharePoint 2010.

    John


    MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
    My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and The SharePoint 2007 Disaster Recovery Guide.
    My blog: My Central Admin.

    Monday, July 30, 2012 1:29 PM
  • This article has the correct information:

    "SharePoint sandboxed solutions are deprecated in SharePoint 2013 Preview in favor of developing apps for SharePoint, but sandboxed solutions can still be installed to site collections on SharePoint 2013 Preview"

    http://msdn.microsoft.com/en-us/library/office/apps/jj163114(v=office.15))

    So yes, the prefered model and future of the SharePoint platform (from an extensibility perspective) is to build apps.

    Thank you for your interest on the preview!


    Wednesday, September 12, 2012 6:20 PM
    Moderator

All replies

  • Hi,

    Read this nice article

    http://www.andrewconnell.com/blog/archive/2012/07/16/understanding-sharepoint-2013-apps-aka-apps-101.aspx


    Regards,
    Fadi Abdulwahab, SharePoint Consultant
    http://blogs.msdn.com/b/fabdulwahab
    http://sqlgoogler.blogspot.com/

    Monday, July 30, 2012 8:23 AM
  • It's not a replacement, it's an addition to the spectrum of possibilities. Sandboxed solutions allow you to execute code in safe way (with limited options), apps for SharePoint allow you to use a separate application server(s) outside of the SharePoint farm leveraging the matured client OMs or REST api. A great advantage of the app model is that it guarantees the farm to be unbohtered by any performance problems created by custom apps.

    On the other hand, a scenario where sandboxed solutions def. remain useful is a small farm where you don't want to manage an additional app server (and have the extra cost) but you do want to be able to execute custom code in a safe way.


    Kind regards,
    Margriet Bruggeman

    Lois & Clark IT Services
    web site: http://www.loisandclark.eu
    blog: http://www.sharepointdragons.com

    Monday, July 30, 2012 8:38 AM
  • One other thing to note about sandbox solutions is that Microsoft is deprecating them in SharePoint 2013. This means that the functionality will still be available for use in SharePoint 2013, but primarily for backwards compatibility with existing solutions built using the sandbox solution approach. Microsoft's guidance is that if you are building new applications that in the past you would have deployed as sandbox solutions, you should use the new App model for those solutions instead of using sandbox solutions. They took a similar approach in SharePoint 2010 with the STSADM command line administration tool when it was deprecated in favor of the SharePoint 2010 Management Shell and the numerous PowerShell cmdlets deployed with that tool. STSADM is still available in SharePoint 2010, but mainly just to allow for older scripts and tools that use STSADM to still function with SharePoint 2010.

    John


    MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
    My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and The SharePoint 2007 Disaster Recovery Guide.
    My blog: My Central Admin.

    Monday, July 30, 2012 1:29 PM
  • "Microsoft's guidance is that if you are building new applications that in the past you would have deployed as sandbox solutions, you should use the new App model for those solutions instead of using sandbox solutions."

    Can you please elaborate on this? what is this new App model which we can use instead of sandbox solutions? Whether it is sharepoint online apps? or something else? whether we can embed the contents of sandbox solutions like visual webpart and sever side code/.net blocks.sharepoint api inside an app?

    Thanks and regards,

    Mishal

    Tuesday, August 28, 2012 6:33 AM
  • Take a look at this - http://jopx.blogspot.be/2012/08/getting-started-with-building-apps-for.html for a quick intro or check out the developer videos specifically around SharePoint 2013 apps - http://msdn.microsoft.com/en-us/office/apps/fp123626.aspx .  If you only want to know more about apps - there's about 7 hours of video material - see here - http://jopx.blogspot.be/2012/09/sharepoint-2013-app-developer-videos.html  - for an overview of the videos which are relevant for SharePoint 2013 app developer.

    I personally don't think that apps are the complete answer - one of the things I'm wondering about is how you will build for example site templates - SharePoint 2010 introduced the new webtemplate feature to allow you to deploy site templates without requiring a farm solution - this does not seem to have a counter part within the app framework.

    Interesting background material on this subject - see

    http://social.technet.microsoft.com/wiki/contents/articles/13373.sharepoint-2013-what-to-do-farm-solution-vs-sandbox-vs-app.aspx

    Rgds,

    Joris [http://jopx.blogspot.com]

    Monday, September 3, 2012 8:53 PM
  • This article has the correct information:

    "SharePoint sandboxed solutions are deprecated in SharePoint 2013 Preview in favor of developing apps for SharePoint, but sandboxed solutions can still be installed to site collections on SharePoint 2013 Preview"

    http://msdn.microsoft.com/en-us/library/office/apps/jj163114(v=office.15))

    So yes, the prefered model and future of the SharePoint platform (from an extensibility perspective) is to build apps.

    Thank you for your interest on the preview!


    Wednesday, September 12, 2012 6:20 PM
    Moderator
  • Totally agree with this statement.

    Here is a perspective for those who need to proceed with SandBox development for SP2010, even though SP2013 doesn't favor it: 

    You feel cheated since MSDN says that Sandboxed solutions are deprecated in SP2013 Preview? Be hold!

    Thursday, September 13, 2012 6:48 PM
  • In addition, SharePoint 2013 has sandboxed solutions baked into the Design Manager that is available for publishing sites. In order to deploy a design package that's put together on a development site, SharePoint packages all the design files (CSS, HTML, etc.) into a sandboxed WSP package that you then migrate to your production environment and deploy. 

    I do agree with the best practice of utilizing the app framework if your requirements support it but I believe that sandboxed solutions will continue to get used in select scenarios.

    ~Jason
    http://cribbet.com

    • Proposed as answer by Phillip Capiral Saturday, December 22, 2012 3:46 AM
    Monday, November 5, 2012 6:03 AM
  • I disagree that it is a replacement.  I strong agree that any custom code development should be moved towards apps instead of sandbox.  However, there is still a business need for sandbox solutions in order to provision lists and content types to the host web.  In some cases, you do not want lists and content types to be in an app web because you want it available in search, content types available to sub-sites.  

    So my question would be what is the best way to deploy site content types and lists?  you cant do it through an app, the only way i see in a cloud solution is to use sandbox?  

    Any thoughts?

    Saturday, December 22, 2012 3:16 AM
  • Custom code can be moved to apps, but it has to be evaluated if an app is the right thing for it. I started with decision framework that should help to do chose the right approach based on your needs. It considers the use of the different App types, Solutions, CSOM with a .NET client and PowerShell Scripts.

    Please share your viewpoints and opinions. 

    http://www.fiechter.eu/blog/Lists/Posts/Post.aspx?ID=39&mobile=0

    Tuesday, April 2, 2013 10:48 AM
  • Thank You.My doubt got resolved :)
    Tuesday, February 18, 2014 5:51 AM