{"id":251,"date":"2010-05-13T17:38:06","date_gmt":"2010-05-13T15:38:06","guid":{"rendered":"http:\/\/www.itidea.nl\/wordpress\/?p=251"},"modified":"2015-09-08T20:32:22","modified_gmt":"2015-09-08T18:32:22","slug":"sandboxed-solutions","status":"publish","type":"post","link":"https:\/\/www.itidea.nl\/index.php\/sandboxed-solutions\/","title":{"rendered":"Sandboxed solutions"},"content":{"rendered":"

Sandboxed solutions are deployed to the database. This means that no files within the sandboxed solution will ever touch the file system of the server. Even dlls, xml files and aspx pages will be deployed to the database.<\/p>\n

In Central Administration ensure that the Microsoft SharePoint Foundation Sandboxed Code Service is running on every server in the Farm where sandboxed solutions will be deployed and running.
\nSandboxed solutions run within a special process, the Sandbox Worker Process (SPUCWorkerProcess.exe), part of this service.<\/p>\n

The visually difference between a sandboxed and a farm solution in Visual Studio 2010 are:<\/p>\n

    \n
  1. the property Sandboxed Solution (Project properties): true for sandboxed, false for farm solution<\/li>\n
  2. AssemblyInfo.cs: [assembly: AllowPartiallyTrustedCallers()] is present in a sandboxed solution, not in a farm solution.<\/li>\n<\/ol>\n

    Sandboxed solution are wsp packages, deployed from solution gallery at site collection level by site collection administrators. The packages are isolated to site collection it is deployed to.
    \nThe solution gallery also displays resources consumed today and average usage the last 14 days.<\/p>\n

    When using sandboxed solutions a farm administrator can assign resource points to a site collection. The default quota is 300 points per day and points are calculated based on 14 different metrics:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Resource<\/strong><\/td>\nDescription<\/strong><\/td>\nUnits<\/strong><\/td>\nResources per point<\/strong><\/td>\nLimit<\/strong><\/td>\n<\/tr>\n
    AbnormalProcessTerminationCount<\/td>\nAbnormally terminated process<\/td>\ncount<\/td>\n1<\/td>\n1<\/td>\n<\/tr>\n
    CPUExecutionTime<\/td>\nCPU Execution Time for site<\/td>\nseconds<\/td>\n3600<\/td>\n60<\/td>\n<\/tr>\n
    CriticalExceptionCount<\/td>\nCritical Exception Events<\/td>\nEvents<\/td>\n10<\/td>\n3<\/td>\n<\/tr>\n
    InvocationCount<\/td>\nSolution Invocation Events<\/td>\nEvents<\/td>\n<TBD><\/td>\n<TBD><\/td>\n<\/tr>\n
    PercentProcessorTime<\/td>\n% CPU usage by solution<\/td>\n%<\/td>\n85<\/td>\n100<\/td>\n<\/tr>\n
    ProcessCPUCycles<\/td>\nSolution CPU cycles<\/td>\ncycles<\/td>\n1×10^11<\/td>\n1×10^11<\/td>\n<\/tr>\n
    ProcessHandleCount<\/td>\nWindows handles count<\/td>\nitems<\/td>\n10000<\/td>\n10000<\/td>\n<\/tr>\n
    ProcessIOBytes<\/td>\nWindows handles count<\/td>\nitems<\/td>\n0<\/td>\n1×10^8<\/td>\n<\/tr>\n
    ProcessThreadCount<\/td>\nThread count in overall process<\/td>\nThread instances<\/td>\n10000<\/td>\n200<\/td>\n<\/tr>\n
    ProcessVirtualBytes<\/td>\nMemory consumed<\/td>\nBytes<\/td>\n0<\/td>\n1×10^9<\/td>\n<\/tr>\n
    SharePointDatabaseQueryCount<\/td>\nNumber of SharePoint database queries<\/td>\nQuery instances<\/td>\n20<\/td>\n100<\/td>\n<\/tr>\n
    SharePointDatabaseQueryTime<\/td>\nElapsed time to execute query<\/td>\nseconds<\/td>\n120<\/td>\n60<\/td>\n<\/tr>\n
    UnhandledExceptionCount<\/td>\nNumber of unhandled exceptions<\/td>\nUnhandled exception instances<\/td>\n50<\/td>\n3<\/td>\n<\/tr>\n
    UnresponsiveProcessCount<\/td>\nNumber of unresponsive processes<\/td>\nUnresponsive process instances<\/td>\n2<\/td>\n1<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    These metrics were chosen because they impact the health and stability of the server. The use of resources that have a higher impact on the server will cost you more points.
    \nWhen the sandboxed solutions in a site collection use more than the assigned amount of points in a single day the sandboxed solutions in that particular site collection are shut down by SharePoint. This means that end users won\u2019t be able to use the functionality of any sandboxed solution in that specific site collection until the resource points are reset. The following message will be displayed to the user:
    \n<\/a>\u00a0\"ExceededResourceUsageQuota\"<\/a><\/p>\n

    The quota is per day, so after 24 hours the site collection will be unlocked and sandboxed solutions in that site collection can be used again. These 24 hours can be adjusted because this is a timerjob default scheduled every 24 hours: Solution Daily Usage Update.<\/p>\n

    Some important notes:<\/p>\n