Posts

Showing posts from December, 2010

How to Build and Deploy a Web Part in MOSS 2010

When i was created my first MOSS 2010 solution i have taken the help of my best online friend Google ;).I found a very good blog on this topic so i m not going to write the steps .Please go through this link http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2010/02/15/intro-to-sharepoint-2010-development-how-to-build-and-deploy-a-web-part.aspx If find any difficulty please make comment.

Change Deployment type & Debug site URL for sandbox & Farm solution in MOSS 2010

Image
When i created first time MOSS 2010 solutions (sandbox as well as farm) than one very first thing strikes me that is how to change the type of solution like for example sandboxed to farm or vice versa and how to change the debugging site path. so we can change these by property window. There is two properties there one is sandboxed solution(True/false) & another one is site url.please see screenshot.;)

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. ;)

Limitation of sanbox solution

No access to sharepoint.webcontrols namespace No elavation privileges 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/

Benefits of using sandbox solution

The first benefit of using sandbox solution is we can directly deploy this solution on production sharepoint server without any risk because it's not affecting any other server process outside the sandbox. Sitecollection administrator can deploy this solution . Scalability & flexibility are increased because sandbox runs in the separate process that can be restricted by quotas and their effect on farm can be monitored. The solution does not have to be modified or recompiled if it is moved from the sandbox to running directly on the farm.

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...