Farm solution Vs Sandbox solution in SharePoint 2013

In this post, I will briefly explain What’s the difference between deploying solution as farm solution vs sandbox solution?

Farm Solution Vs Sandbox Solution

Here we will show the main differences SharePoint Farm Solution and SharePoint Sandbox Solution

Farm solution Vs Sandbox solution in SharePoint 2013

SharePoint Farm Solution

  1. Farm solutions, which are hosted in the IIS worker process (W3WP.exe), Run the code that can affect the whole farm.
  2. When you debug a SharePoint project whose Sandboxed Solution property is set to “farm solution”
  3. The system’s IIS application pool recycles before SharePoint retracts or deploys the feature so as to release any files locked by the IIS worker process.
  4. Only the IIS application pool serving the SharePoint project’s site URL is recycled.

SharePoint Sandboxed Solution

  1. Sandboxed solutions, which are hosted in the SharePoint user code solution worker process (SPUCWorkerProcess.exe), run code that can only affect the site collection of the solution.
  2. Because sandboxed solutions do not run in the IIS worker process, neither the IIS application pool nor the IIS server must restart.
  3. Visual Studio attaches the debugger to the SPUCWorkerProcess process that the SPUserCodeV4 service in SharePoint automatically triggers and controls.
  4. It is not necessary for the SPUCWorkerProcess process to recycle to load the latest version of the solution.


In conclusion, we have briefly explained the main difference between Farm solution Vs Sandbox Solution?

Applies To
  • SharePoint 2013.
  • SharePoint 2010.
You might also like to read

1 thought on “Farm solution Vs Sandbox solution in SharePoint 2013”

  1. Pingback: Sandboxed Solution Considerations | SPGeeks

Leave a Reply

Scroll to Top