But Why Sandboxed Solutions?
Today, in SharePoint Server 2007, solutions are deployed in the farm level though you can activate features per web application or site. There is no proper way you can centrally manage/administer these solutions in a shared environment per web application or site. With sandboxed solutions, administrators can now allocate quotas, monitor the usage and also prevent excessive usage of resources by the solution. But yes, you are limited in the functionality what the solution can access, but as long as the solution scope is not beyond the site level, it is always better to build sandboxed solutions.
Surprisingly, Sandboxed solutions are going to play a major role in Microsoft Online Services very soon :)
Building a Sandboxed Solution
Building a Sandboxed solution is as simple as building a normal SharePoint application (Web Part, User Control etc.,).
Refer the following MSDN Article to find out more about Sandboxed Solutions. From MSDN:
The following capabilities and elements are available in sandboxed solutions:
The following capabilities and elements are not available in sandboxed solutions:
- List definitions
- List instances
- WebTemplate Feature element instead of Webtemp.xml
- Content Types/Fields
- Feature callouts
- Web Parts derived from WebPart
- Event receivers
- Custom Actions
- Custom Action groups
- HideCustomAction element
- Content Type Binding
- Web Application-scoped Features
- Farm-scoped Features
Click here to read the original article by chakkaradeep
Is the above link useful to you? Let us know your feedback, it will help us to improve our posting(s). or You can send your feedback linkOblast.