Microsoft Office Tutorials and References
In Depth Information
M A N A G I N G F A R M S O L U T I O N S
Managing solutions is very much like managing farm features in that you need to use STSADM
or PowerShell to add the solution (and remove it). However, you can choose to deploy or retract
a solution once it’s added to SharePoint using the Solution Management page. If there are no
solutions available at the farm level, the Solution Management page will suggest you use the
STSADM -o addsolution command to add one (Figure 11.41). If there have been solutions
added to the farm, they would be listed here, along with their deployment status.
Solutions are really files packaged together in a CAB file with the .wsp extension. A solution
can be as big as a site definition, containing site templates and their features and web parts, or as
small as a single feature and its supporting files.
Solutions are often made of features that can be scoped to be activated at different levels
of SharePoint. Thus, they can add things such as workflows to lists at the site collection level,
new menu options to sites, new functionality to site settings, and more. When a solution is
deployed to a web application, that only means that all of the site collections or sites in that
particular web application can have access to the new features, depending on how they’re
written. See Chapter 15 for a demonstration of how to add and deploy solutions.
M A N A G E U S E R S O L U T I O N S
New with SharePoint Foundation, user solutions let you manage solutions uploaded and applied
at the site collection level, allowing more freedom and flexibility for users other than farm
administrators to deploy solutions. What makes it possible to deploy solutions that aren’t
regulated by the farm administrator is that they can be “sandboxed,” meaning that their resources
can be constrained, their reach can be limited, and some solutions can simply be blocked.