Solutions Sandbox – Limitaciones

Hasta el día de hoy, estas son algunas limitaciones de las soluciones sandboxed. Con la nueva versión de Visual Studio se eliminarán algunas de estas limitaciones: http://todosharepoint.blogspot.com/2012/01/what-new-sharepoint-development-in.html

• Can’t deploy files to disk or deploy assemblies to GAC. Can you imagine how limiting this can be? Think workflows.

• Cannot access the cache object from a sandboxed web part.

• Cannot access the ScriptManager from a sandboxed web part.

• Sandbox does not support re-direction – no Response.Redirect, no Server.Transfer,  no SPUtility.Redirect.

• Can’t access SharePoint.WebControls: you can't create a Web Part that uses any of the built in controls which you can use in SharePoint Designer!

• No support for SharePoint.WebPartPages namespace.

• SPUtility.SendEmail is blocked. In short, can’t send emails. You can use the ASP.NET email classes

• Can’t do anything that the CurrentUser can’t do. No elevation of privilege.

• Can’t really export a sandboxed web part. All it’ll do is export the SPUserCodeWebPart. You don’t want that.

• Can’t do HTTP calls. No making web service calls over the internet.

• Can’t do anything across SPSite boundaries. (I know, I know, it’s a feature not a bug!!!)

• All sandboxes share the same worker process (SPUCWorkerProcess.exe). Makes me wanna revisit the very definition of a Sandbox!!!

• Cannot use UpdatePanel (to addition to ScriptManager limitation)

• There is a very confusing bug/feature. Sometimes when you are working on a Sandbox Solution and deploy it often while debugging/testing/etc – changes do not fully apply (more to say – they do apply, but wrongly, which is very confusing). To fix it, you need to restart a Visual Studio. At some point I began restarting it before every deploy. Seems there is some kind of caching of schema.xml and elements.xml.

• ActionMenu : HideCustomAction and CustomActionGroup menus are not working (so you cannot create your own application sub-group in “Site Settings” for instance),

• Visual WebParts are not usable, but some clever guys put a ”Visual WebPart (Sandbox)” template for SharePoint 2010 in Visual Studio Gallery.

• ASP.NET 2.0 web controls are not fully working (those that are using “WebResource.axd” for internal binaries resources, as .axd extension is not allowed),

• PropertyBags of SharePoint Object model are not accessible,

• Modules outside of the current site are not allowed, like BCS or UserProfile,

• Global folders like “_layout” & “resources” are not authorized.