Limitation of sanbox solution

  1. No access to sharepoint.webcontrols namespace
  2. No elavation privileges
  3. sputility.sendmail method is blocked in sanbox solution
Go through this very good blog for some other restrictions:
http://www.endusersharepoint.com/2010/01/08/sharepoint-2010-sandbox-solutions-are-bad/

Comments

Post a Comment

Popular posts from this blog

How to deploy sandbox solution from one environment to other

Deploying sandbox solution from one sitecollection to other is a simple process.Assuming you created a sandbox solution for your Dev environment.& now you want to deploy it on other sitecollection. Save wsp file of solution from your dev sitecollection solution gallary which u can find inside sitesettings Now open your solution gallary of prod sitecollection & upload wsp there. Do not forget to activate that. Once u activated that solution go on your page and add webparts. ;)
Read more

Difference between sandbox & farm solution

When we create MOSS 2010 solution there are two options for solution type one is sandbox solution and another one is farm solution. people are very eager to know wht is the difference between them. sandbox solution: sandbox solution are solution that run in the context of sitecollection.it's resticted.The solution can only access resources of that particulat sitecollection where it was deployed. By using sandbox solution we can deploy webparts,event receivers,feature receivers,Custom microsoft designer workflows activities,microsoft infopath business logics.It's cannot connect to resources that are not located on local server and can't access database as well as resources in different sitecollections.It is monitored & limited by quotas set by farm administrator. who can deploy sandbox solution :If the solution contains assembly than only sitecollection administrator deploy it and if the solution does not contains assembly than a user who has full control on root of site...
Read more