Skip to main content

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

Popular posts from this blog

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

Users do not show up in SharePoint People Search or People Picker

I had this issue with people picker in a classic mode web application in SharePoint 2013 and this site is in 2010 mode - users in certain sub-domains would not show up in People Picker. I was aware of stsadm commands to fix this and we ran the stsadm command to hook up people picker with another domain some time back. The latest issue was that people picker was not returning users from the root domain and few sub domains. After researching on the internet I found (contrary to my thoughts) that we could use PowerShell and not just stsadm to map People Picker to domains. It is a good idea to first check what domains are added/mapped to the web application using the following commands: $wa = Get-SPWebApplication -Identity http://mywebapp.com #List the Domains $wa.PeoplePickerSettings.SearchActiveDirectoryDomains This will list the domains currently People Picker is looking up for that web application. I used the following script to map our AD forest to People Picker:

Report Server has encountered a SharePoint error. ( rsSharePointError)

I was receiving this error on the "Report Server Web Service URL" on our SharePoint farm: Report Server has encountered a SharePoint error. ( rsSharePointError) Access to this Web Site has been blocked. Please contact the administrator to resolve this problem. This site URL is configured via Central Administration > Configure Reporting Services Integration > Reporting Services Integration if Reporting Server feature/Add-in is installed on the farm. After doing some research I found out that this page somehow enumerates through entire site collections before it throws this error. As part of troubleshooting step I checked if the domain user configured for reporting service is has sufficient privileges in the farm and also as local admin of the sql box, but this did not solve the issue. We raised this issue with the vendor and they made us update our SQL Server 2005 to latest SP and CU; still we had the error. The reason was nobody was sure if this er