Don’t break that sandbox

Posted on 4/17/2011 @ 8:03 PM in #SharePoint by | Feedback | 417 views

Hmm .. I hear that some soldiers are spreading rumors that it is OKAY to edit the WSS_Sandbox trust level inside of SharePoint. Afterall, it is just .NET code right? And it’s just a CAS policy, so why not make that tempting little tweet, and well – all I wanna do is call web services! Ummmm ..




Yes I know it’s just .NET code! But Microsoft has spent a great deal of time, resources, and thoughts in crafting up the boundary of what a sandbox solution can do, and what it cannot do. Soon as you make that tiny little tweak to allow calling web services, you just opened a bunch of security holes in your SharePoint installation. Not to mention, you broke the first cardinal rule of your SharePoint solutions, which is,

“No Microsoft files were hurt in the building of this solution”

And given that we are all eventually going towards the cloud – making the sandbox fit your applications, rather than your applications fitting the sandbox is probably not the best idea. You are creating unsupported code that won’t upgrade nicely, and it won’t work in the cloud.

So, next time, if anyone tells you to edit your WSS_Sandbox .. JUST SAY NO!

Sound off but keep it civil:

Older comments..