If somebody like the post and its helpful in your work then, add comments.

Wednesday, October 6, 2010

SharePoint 2010: What is Sandbox Solution?


Many of the SharePoint are working on the SharePoint for a long time. Many of then also started working in the SharePoint 2010. Their are many things that SharePoint 2010 made easier then from SharePoint 2007/Moss. Many improvements are given to the SharePoint to that it can build a better solution.

If you have been reading about exciting new features of SharePoint 2010 you probably heard about something called SandBox Solutions.  What is the Sandbox solution?

SharePoint is a rich development platform with a large community actively developing solutions. The challenge, however, has always been the balance between creating solutions and deploying them in a way that you can trust will not damage or impair the SharePoint farm. Sandboxed solutions, new in SharePoint 2010, address this by allowing site collection administrators to deploy solutions that are safe to run. Sandboxed solutions are restricted to running under a subset of the SharePoint API and the framework can monitor these solutions and shut down any that risk the stability of the farm.

SandBox Solutions support the following SharePoint item types:

  • List definitions
  • List instances
  • Content Types/Fields
  • Navigation
  • Web Parts derived from WebPart
  • Event receivers
  • Custom Workflow Actions
  • Workflows


For developing a sandbox solution you have to just create a new blank SharePoint Solution in Visual Studio 2010. Go to properties of the solution and change the solution type to true.


Deploying Sandboxed Solutions

The structure of a sandboxed solution is very similar to a farm solution, which generally runs with full-trust permissions. The main differences lie in how a sandboxed solution is deployed and in the process that hosts the solution (which determines whether a solution is a sandboxed solution or a farm solution). This means that the same sandboxed solution can run with full trust when it’s deployed at the farm level and with partial trust when it’s deployed at the site collection level.



  1. Nice Info..... :). Helpful for the guys who have just started development in SharePoint 2010.

  2. Disadvantages of Sandbox solutions:
    1. No support to Microsoft.SharePoint.WebPartPages namespace.
    2. It’s more secure, can’t elevate privileges and leads to more complex codes.
    3. Making web service calls over the internet, or accessing code that is not marked to allow partially trusted callers are not supported. You also can’t deploy files to disk or add assemblies to the GAC in a sandboxed solution, and security-related functionality, such as running RunWithElevatedPriviledges and other SPSecurity methods, is not allowed.
    4. No support to SPUtility.SendEmail namespace for sending mails.

  3. Hi Hitesh,

    Well the solution does not have the disadvantage. First we have to consider the scenarios where the solution fit like simple publishing site with page layouts and master page.


  4. Sharepoint 2010 can save your business money by putting intranet, extranet, and internet sites all on a one platform. It also means people can save time by doing their jobs more quickly - they will have faster access to the information they need.