The basic architecture of a SANDBOX solution.
Item Template
|
Sandbox
Compatible
|
Notes
|
Visual Web Part
|
No
|
Requires ASCX
file be
installed on SharePoint Servers
|
Visual Web Part
(Sandboxed)
|
Yes
|
Provided by
installing the
Visual Studio 2010 SharePoint Power Tools
|
Web Part
|
Yes
|
|
Sequential
Workflow
|
No
|
Requires workflow
solution be deployed as Farm Solution
|
State Machine
Workflow
|
No
|
Requires workflow
solution be deployed as Farm Solution
|
Business Data
Connectivity Model
|
No
|
Requires BCS
solution be
deployed as a full-trust solution;
feature not supported in
SharePoint Online
|
Application Page
|
No
|
Requires ASPX
page be
deployed to SharePoint Server
|
Event Receiver
|
Yes
|
|
Module
|
Yes
|
|
Content Type
|
Yes
|
|
List Definition
from Content Type
|
Yes
|
|
List Definition
|
Yes
|
|
List Instance
|
Yes
|
|
Empty Element
|
Yes
|
|
User Control
|
No
|
Requires ASCX
file to be
installed on SharePoint Servers
|
The main things we can package with a SANDBOX solution
1.
Web Parts
2.
Event receivers
3. Feature receivers
4.
Custom Microsoft SharePoint Designer
workflow activities
5. Microsoft InfoPath business logic
Limitations
1. User must
be a site collection administrator to deploy a sandbox solution
2. Sandbox
assemblies run under separate service (SPUserCodeV4)
3. Default
CAS (No file access, no web service calls, limited access to SharePoint object
model)
4. No support
for “Visual WebParts” (ie. No support to “Microsoft.SharePoint.WebPartPages.WebPart”.
It is only support to System.Web.UI.WebControls.WebParts)
No comments:
Post a Comment