Get-SPUserSolution
Published: May 12, 2010
Returns a specified sandboxed solution.
Get-SPUserSolution [[-Identity] <SPUserSolutionPipeBind>] -Site <SPSitePipeBind> [-AssignmentCollection <SPAssignmentCollection>]
Parameters
| Parameter | Required | Type | Description | ||
|---|---|---|---|---|---|
|
Identity |
Optional |
Microsoft.SharePoint.PowerShell.SPUserSolutionPipeBind |
Specifies the sandboxed solution to get. The type must be a valid name of a user solution (for example, UserSolution1); or an instance of a valid SPUserSolution object. |
||
|
Site |
Required |
Microsoft.SharePoint.PowerShell.SPSitePipeBind |
Specifies the site collection that contains the sandboxed solution. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid URL, in the form http://server_name; or an instance of a valid SPSite object. |
||
|
AssignmentCollection |
Optional |
Microsoft.SharePoint.PowerShell.SPAssignmentCollection |
Manages objects for the purpose of proper disposal. Use of objects, such as SPWeb or SPSite, can use large amounts of memory and use of these objects in Windows PowerShell scripts requires proper memory management. Using the SPAssignment object, you can assign objects to a variable and dispose of the objects after they are needed to free up memory. When SPWeb, SPSite, or SPSiteAdministration objects are used, the objects are automatically disposed of if an assignment collection or the Global parameter is not used.
|
Detailed Description
The Get-SPUserSolution cmdlet returns a specified sandboxed solution. If the Identity parameter is not specified, this cmdlet returns the collection of sandboxed solutions in the site collection. A user solution is a sandboxed solution.
Input Types
Return Types
Errors
| Error | Description |
|---|---|
|
|
|
| Exceptions | Description |
|---|---|
|
|
|
-----------------EXAMPLE---------------------
Get-SPUserSolution -Site http://sitename
This example displays information about sandboxed solutions in the site http://sitename.
Change History
| Date | Description | Reason |
|---|---|---|
|
May 12, 2010 |
Initial publication |
|

Note: