Get-SPVisioServiceApplication
Published: July 16, 2012
Applies to: SharePoint Server 2013 Enterprise
Returns properties of a Visio Services application or a collection of Visio Services applications.
Get-SPVisioServiceApplication [[-Identity] <SPVisioServiceApplicationPipeBind>] [-AssignmentCollection <SPAssignmentCollection>]
Parameters
| Parameter | Required | Type | Description | ||
|---|---|---|---|---|---|
| Identity | Optional | Microsoft.Office.Visio.Server.Cmdlet.SPVisioServiceApplicationPipeBind | Specifies the Visio Services application to get. The type must be a valid GUID, in the form 12345678-90ab-cdef-1234-567890bcdefgh; a valid name of a Visio Services application (for example, MyVisioService1); or an instance of a valid SPVisioServiceApplication 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-SPVisioServiceApplication cmdlet retrieves the settings of the specified Visio Services application. If the Identity parameter is not specified, this cmdlet returns the collection of Visio Services applications in the farm.
Input Types
Return Types
-----------------------EXAMPLE 1-------------------------
Get-SPVisioServiceApplication
This example returns a collection of all Visio Services applications in the farm.
-----------------------EXAMPLE 2-------------------------
Get-SPVisioServiceApplication "VGS1"
This example returns properties of the VGS1 Visio Services application.
Change History
| Date | Description |
|---|---|
| July 16, 2012 | Initial publication |

Note: