sd

SharePoint 2013 has its own system to install extensions to the administrative functions of SharePoint that is different from other Windows applications and platforms. No MSI or ClickOnce technology is involved. Instead, assemblies, XML and other files in the extension are grouped into a single file, called a solution package. A solution package is priced based on .cab format but an extension .wsp file. The package may contain the features of SharePoint and all its child components in addition to certain types of components that are not implemented in characteristics. Administrators farm load packages in a storage location of all the farm from where it can be implemented and activated features.
Unlike Accessories SharePoint farm solutions contain code that is deployed on SharePoint servers and makes calls to the object model of SharePoint Server. These assemblies are always executed with full confidence. Furthermore, the characteristics of farm solutions can have as wide scope as site collection, Web application, or the entire farm, besides the field of Web site features SharePoint Ins. Sometimes these aspects of farm solutions create reluctant to install, farm managers, unless they come from a known and trusted source. Therefore, you must develop SharePoint extensions that are primarily for use by end users as complements SharePoint solutions do not farm. Solutions should be used farm customizations for SharePoint administrative functions, such as custom timer jobs, custom Windows PowerShell cmdlets and extensions of central government. For more information on the benefits of SharePoint complements and uses of farm solutions,