SHAREPOINT 2010 Training

Configuring and Administering Microsoft SharePoint 2010

SHAREPOINT 2010 Training

limitations of sandboxed solutions sharepoint 2010
SharePoint 2010 Sandbox limitations:

1. No Security Elevation - RunWithElevatedPrivileges which runs the specified block of code in application pool account(typically System Account) context is not allowed in Sandbox code. SPSecurity class also not allowed to use in Sandbox.
2. No Email Support - SPUtility.SendMail method has been blocked explicitly in Sandbox, However .Net mail classes can be used to send mails. Additionaly sandbox won't allow to read Farm SMTP address. So developers has to specify the SMTP address in code itself(may be some other workaround).
3. No Support to WebPartPages Namespace - Sandbox won't allow to use Microsoft.SharePoint.WebPartPages namespace.
4. No Support to external Webservice - Internet web service calls are not allowed to ensure security in Sandbox solutions. Allow Partially Trusted code also can't be accessed within Sandbox.
5. No GAC Deployment - Sandbox solutions are not stored in File System(Physical path) and assemblies can't be deployed to Global Assembly Cache(GAC). But it's available on C:\ProgramData\Microsoft\SharePoint\UCCache at runtime. Note the ProgramData is a hidden folder.
6. No Visual Webparts - Visual Studio 2010 by default won't allow to create Visual Webparts to deploy as sandbox solution. But with Visual Studio PowerTools extensions(downloadable from Microsoft MSDN website) Visual Webparts can be developed and deployed as sandbox Solutions.
7. If you deploy same solution in mutliple site collections and in case when you want to upgrade that solution, it needs to be done one by one.
8. First, there are two types of Web Parts in Visual Studio—visual Web Parts and standard WebParts. A visual Web Part contains an .ascx control that you can use to visually design the look of the Web Part. Unfortunately, you cannot use visual Web Parts in the sandbox because sandboxed solutions can’t deploy files to the Web front end, which is where the .ascx files need to be deployed. This means that you must create a standard Web Part.
9. Almost all classes in the Microsoft.SharePoint.WebControls namespace are not available, which means you are mainly restricted to ASP.NET controls in sandboxed solutions.
10. Images, script files, and Features in sandboxed solutions are deployed to the content database, not to the file system of the front end servers.
11. Application pages, user controls (.ascx files), and localization resource (.resx) files cannot be deployed with a sandboxed solution. (There are other ways to localize sandboxed solutions.


What is Sharepoint 2010
http://sharepoint.microsoft.com/en-us/product/capabilities/Pages/default.aspx