What is sandboxed solution? Sandboxed solution is a new concept introduced by Sharepoint 2010. Solution refers to your custom deployment.CodeOn the Sharepoint Server, user-defined code is not available in actual projects, but user-defined code is also the main source of energy consumption and headaches.
Sandboxed solution is the custom code running in a Security Sandbox (save sandbox. it runs under the limits of some unacceptable standards, so it can only do some things, and some things cannot be done. the vast majority of these prohibited things are the cause of headaches just mentioned.
Sandboxed solution can be monitored by administrators at two levels. site set administrators can monitor sandboxed solution through site actions-> site settings-> solution gallery. Field administrators can monitor sandboxed solution based on the Management Center page of each site set.
The field administrator can not only monitor sandboxed solution, but also set the resource allocation ceiling for sandboxed solution through standard quota mechanism on the Management pages of different site collections. resource allocation is limited by 16 indicators, which are achieved through a point-based system. the number of points allocated by the field administrator for the site set. if any sandboxed solution causes the allocation point to exceed the limit, all sandboxed solution on that site set will be stopped until the 24-hour reset of the timer job that continues running) site set to restore them. also, when you run under the quota, if you want to do something bad, such as formatting the C drive, your execution will also be blocked, at the same time, a certain number of quotas will be deducted. If your solution tries to do bad things again, the result can be imagined, once again blocked, and then more quotas will be deducted. for each of these indicators, you can set an absolute upper limit before the execution is stopped, or choose to increase the resource point value without blocking resource allocation. it is useful when you want to stop execution and add resource points.
The farm administrator can also prevent execution of a sandboxed solution.
Finally, if your code is much restricted and monitored, but in general it rarely gets into trouble in the server environment, you will be more confident during deployment.
Also, the biggest advantage of sandboxed solution is that it can be deployed by the site set administrator, and they will be deployed in the solution Gallery of the site set. Furthermore, if your solution does not require deploymentProgramAssembly, so even those who have full control over the site set can be deployed, which greatly reduces the headache of the field administrator.
This is a simple introduction to sandboxed solutions. They are restricted, therefore secure, easy to monitor, easy to manage, and easy to deploy.
The following example helps you understand sandboxed solution, which is simple and does not translate.
I like to think this level of monitoring very much like a family cellphone plan. dad, Mom, sister, and son have a pool of 2000 minutes to share. now if the son somehow starts calling his Russian girlfriend a little too much, everyone's cellphones quit working! Now Dad has to call the phone company, and request the entire family plan to be allowed to run, and the offending solution (the son's cellphone), can now be blocked execution.
From:
Http://blah.winsmarts.com/2009-12-SharePoint_2010_Sandboxed_Solutions__The_basics.aspx