Instal the new Farmside install#
Instal the new Farmside full#

Our recommendation that farm solutions be used primarily for administrative extensions did not apply in SharePoint 2010. 'no code' sandboxed solutions are still viable.

Sandboxed solutions with custom code are deprecated in SharePoint. You will see many references to 'sandboxed solutions' in the SharePoint 2010 SDK. To avoid confusion, keep the following points in mind at all times when using the SharePoint 2010 SDK to develop against SharePoint: Guide to the developer documentation for farm solutionsĭevelopment of farm solutions has changed very little since SharePoint 2010, so this section contains links to the SharePoint 2010 SDK. For more on the advantages of SharePoint Add-ins and the uses of farm solutions, see SharePoint Add-ins compared with SharePoint solutions. Farm solutions should be used for customizations of SharePoint administrative functions, such as custom timer jobs, custom Windows PowerShell cmdlets, and extensions of Central Administration. For this reason, SharePoint extensions that are primarily for use by end users should be developed as SharePoint Add-ins, not farm solutions.

Instal the new Farmside install#

These aspects of farm solutions sometimes make farm administrators reluctant to install them, unless they come from a well-known and trusted source. Moreover, the Features in farm solutions can have scope as wide as the site collection, web application, or whole farm, in addition to the website scope of Features in SharePoint Add-ins.

Instal the new Farmside full#

These assemblies always run with full trust. Unlike SharePoint Add-ins, farm solutions contain code that is deployed to the SharePoint servers and makes calls to the SharePoint server object model. Farm administrators upload the packages to a farm-wide storage location from where they can be deployed and their Features activated.

The package can contain SharePoint Features and all their child components in addition to certain kinds of components that are not deployed in Features. Instead, the assemblies, XML, and other files in the extension are bundled into a single file, which is called a solution package.

No MSI file or ClickOnce technology is involved. SharePoint has its own system for installing extensions to SharePoint administrative functions that is different from other Windows applications and platforms. Get an overview of our documentation about developing, packaging, and deploying administrative extensions to SharePoint using farm solutions.