Welcome to codebanking - Bank your code here
|
Sandboxed Solutions in sharepoint 2010 |
 |
 |
 |
|
Written by Administrator
|
|
Saturday, 30 January 2010 13:31 |
|
Why Sandboxed solution?
In MOSS 2007
Developer build Custom Solutions
Administrator can only secure solution and deploy solution which makes hard to find out what is being done inside code.
In detail
•The product SharePoint releases the burden on IT departments by allowing end-users to be manage the information structure. •This is an important part to the success of SharePoint, the core concept of sites, lists and libraries and provisioning. •However, the real value lies in the customizations that enable you to maximize the potential that sits in the templates provided by SharePoint. •In SharePoint 2007 you still need IT to install and maintain these customizations. This slows down business and impacts IT unnecessarily.
What is Sandboxed solution approach?
Developer build Custom Solutions
SiteCollection Owners deploy , activate and implement the customizations.
Administrator can monitor and check sitecollection usage
Note: Automatic triggers “turn off” custom solutions in a site collection that are too expensive
memory usage.
Concept of Sandboxed Solution: A SharePoint solution has two sides to it. The declarative CAML used to create many components such as list templates and content-types, and the code side in workflow, event receivers or Web parts. Sandboxed solutions can contain all these elements. The solutions are deployed to a special gallery which sits under _catalog like the other built-in galleries.
 |
|
