Farm solution VS Sandbox solution

Here is a comparison between SharePoint 2010 farm solution and Sandbox solution

Feature	Farm Solution	Sandbox Solution
Deploying the solution	The farm solution is added directly to the SharePoint server and then deployed to the farm. It is deployed by the farm administrator.	The Sandbox solution is uploaded using the Solution Gallery interface of the site collection and then activated. And the solution is deployed by the site collection administrator or a user with full privilege.
Running the solution	The farm solution uses an IIS worker process with unrestricted rights.	The Sandbox solution uses a separate worker process to access and execute the data.
Accessing the data	A farm solution has complete access to all the content at the farm level.	A Sandbox solution uses a separate worker process to access and execute the data. This restricts the data availability at the site collection level alone.
Securing the solution	The farm solution is not governed by any access security but the developer can set the code access when packaging the solution.	The Sandbox solution is governed and protected by the .NET Code Access Security or CAS policy.
Monitoring the solution	The solutions deployed in the farm are not monitored.	The site collection administrator monitors the Sandbox solution based on the restrictions provided by the farm administrator.
Balancing the load	The load balancing used in a farm solution depends on the type of solution that is deployed.	The load balancing used in a Sandbox solution is configured outside the sandbox.

Comments

Difference between the architectures of SSPs and SharePoint Service Application

SharePoint 2010 has some new features and components, which help to overcome difficulties such as redundancy and service-sharing that we faced while using SharePoint 2007. Services in MOSS 2007 were implemented with the help of Shared Service Providers or SSPs. But we cannot use the services of one SSP for another SSP. So each SSP has to have its own set of services and applications, which increases redundant data in the farm. For example, different managers in the same organization use a SharePoint site to maintain official data associated with an SSP. This SSP is associated with different services, such as Search service, BDC service, and a user profile service. A project manager in this organization requests an exclusive user profile service to maintain project data security. To provide this, we first need to create a separate SSP for the project manager and then a separate service called user profile service - project name. Next, we need to associate the SSP with ...

SharePoint Designer Workflow Failed to Start - Cancelled by System Account

I was working on a List workflow the other day in SharePoint Designer 2010. This list already had a workflow which was working perfectly fine and I needed another manual workflow in it. No matter what I tried the workflow would fail and would log a message in the history list that Workflow failed to start and it was cancelled by System Account . I observed that the same happened with new workflows in that list, new workflows in other lists and I even tried creating new subsites and workflows were behaving the same way. I googled for a while and there were many suggestions to clear SPD cache which did not help me. I played with SPD 2010 for a while and observed that the workflow xml and xoml files were checked out. I read in some blogs that this could cause this issue as well. I tried to check those files in but then I was greeted with a new error! " Cannot perform this operation. The file is no longer checked out or has been deleted ." I had no clue what was happening...

"Cannot impersonate user for data source" - SSRS reports

We were getting this strange error while viewing our reports in SharePoint that was deployed using BIDS 2005: An error has occurred during report processing. Cannot impersonate user for data source 'datasource' Logon failed I tried many things but nothing worked. I did some research and found many blog posts which suggested me to reapply the password on the datasource file specified in the error message and save it again. That didn't work for me. I saw some check boxes in the data source file that read "Use as Windows Credentials" and "Set Execution Context to this report" and I didn't know what they meant. I unchecked those in my data source and then when the refreshed the page the report started displaying.

My IT Experiences

Search This Blog