Contents
Unlike SharePoint Add-ins, farm solutions contain code that is deployed to the SharePoint servers and makes calls to the SharePoint server object model. These assemblies always run with full trust. Moreover, the Features in farm solutions can have scope as wide as the site collection, web application, or whole farm,…
SharePoint Foundation is not consistent in its terminology with regard to installation and uninstallation of farm solutions. The terms Adding, Deploying, and Activating are the most commonly used to refer to the three steps of installation; but depending on what tool is used to carry out a step, you will see a variety of terminology.
Can a sandboxed farm be used in SharePoint?
Sandboxed solutions with custom code are deprecated in SharePoint. “no code” sandboxed solutions are still viable. Our recommendation that farm solutions be used primarily for administrative extensions did not apply in SharePoint 2010.
Can a sharepoint.dll be called in a sandbox?
Certain methods in Microsoft.SharePoint.dll can be called in sandboxed solutions only if the calling code conforms to certain restrictions on the values of the passed parameters. Also, certain properties in Microsoft.SharePoint.dll are read/write in farm solutions but read-only in sandboxed solutions.
Install SharePoint 2013 on a single server with a built-in database. You can quickly publish a SharePoint site by deploying SharePoint 2013 on a single server that has a built-in database. This configuration is useful if you want to evaluate SharePoint 2013 features and capabilities, such as collaboration, document management, and search.
A solution package has a .cab-based format but a .wsp file extension. The package can contain SharePoint Features and all their child components in addition to certain kinds of components that are not deployed in Features.