Web Deploy GetDependencies Operation

Applies To: Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP

getDependencies

The getDependencies operation returns dependencies on features that Web Deploy cannot synchronize and that you may want to install separately on the destination.

Example

msdeploy -verb:getDependencies -source:webServer

The getDependencies operation helps you to determine components that are being used by a Web site or Web server that you may have to install separately on a destination before you can perform a synchronization. Web Deploy cannot synchronize components that are either not supported by IIS 7 or require you to configure them before they can run correctly on the destination.

The output of getDependencies is displayed in XML format. You do not need to specify the -xml operation setting. The root node of the output is named dependencyInfo.

Sample output

The following command on an IIS 6.0 Web server produces the sample output that follows.

msdeploy -verb:getDependencies -source:webServer60

<dependencyInfo>
    <dependencies>
        <dependency name="AnonymousAuthentication" />
        <dependency name="WindowsAuthentication" />
        <dependency name="BasicAuthentication" />
        <dependency name="ISAPIFilter" />
        <dependency name="FrontPageServerExtensions" />
        <dependency name="DigestAuthentication" />
        <dependency name="ASP" />
        <dependency name="ServerSideIncludeDisabled" />
    </dependencies>
    <apppoolsInUse>
        <apppoolInUse name="DefaultAppPool" definitionIncluded="True" />
        <apppoolInUse name="MSSharePointAppPool" definitionIncluded="True" />
        <apppoolInUse name="WebDavAppPool" definitionIncluded="True" />
    </apppoolsInUse>
    <isapis>
        <isapi dll="C:\WINNT\system32\inetsrv\httpodbc.dll" enabled="False" />
    </isapis>
</dependencyInfo>

GetDependencies Settings

You can use special settings to determine the dependency data getDependencies will return. Multiple settings may be specified in one command. The settings are added on to the getDependencies keyword in a comma-delimited list:

-verb:getDependencies,<setting>[=<value>],<setting>[=<value>], ...

The specified setting or settings will suppress all output from other dependencies. Notice that the use of these settings to filter the output does not necessarily reduce the amount of data that must be processed.

The following describes the settings that you can use with getDependencies.

Setting	allTrigger
Usage	-verb:getDependencies,alltrigger
Description	Returns <trigger> elements for all dependencies. A trigger element contains the absolute path to the location where a dependency was detected or to where a metabase key or metabase property of the dependency was set (for example, <dependency name="AspNet2.0"><trigger absolutePath="/LM/W3SVC/2/ScriptMaps" /></dependency>). For more information about trigger information, see Controlling the Output of Trigger Information.
Example	This example returns all dependencies for an IIS 6.0 Web server. msdeploy -verb:getdependencies,alltrigger -source:webserver60

Setting	appPoolInUse
Usages	-verb:getDependencies,appPoolInUse -verb:getDependencies,appPoolInUse=<appPoolName>
Description	Returns the names of all application pools currently in use, and returns <trigger> elements for each application pool that show the application paths of the applications that are using the application pool.
Example	This example displays the application pools currently in use, and their associated applications, on an IIS 6.0 Web server. msdeploy -verb:getdependencies,apppoolinuse -source:webserver60

Setting	cgi
Usage	-verb:getDependencies,cgi -verb:getDependencies,cgi=<CgiExecutableFilePath>
Description	Returns the names of all applications that depend on CGI modules. When the file path to a CGI executable file is specified, returns all dependencies on the specified file.
Example	This example returns all CGI dependencies on an IIS 6.0 Web server. msdeploy -verb:getdependencies,cgi -source:webserver60

Setting	dependency
Usage	-verb:getDependencies,dependency=<dependency>
Description	Specifies that only dependencies of the type <dependency> be returned. Possible values for <dependency> are: AnonymousAuthentication, ASP, AspNet2.0, Authorization, BasicAuthentication, CGI, ClientCertificateMappingAuthentication, CustomLogging, DefaultDocument, DigestAuthentication, DirectoryBrowse, HttpCompressionDynamic, HttpCompressionStatic, HttpErrors, HttpLogging, HttpRedirect, HttpTracing, IISCertificateMappingAuthentication, IPSecurity, ISAPIExtensions, ISAPIFilter, NetFxExtensibility, RequestFiltering, RequestMonitor, ServerSideInclude, ServerSideIncludeDisabled, StaticContent, WindowsAuthentication.
Example	This example displays IIS 6.0 ASP dependencies. msdeploy -source:webserver60 -verb:getDependencies,dependency=asp

Setting	isapi
Usages	-verb:getDependencies,isapi -verb:getDependencies,isapi=<PhysicalPathToIsapiDll>
Description	Returns the names of all applications that depend on ISAPI modules. When the file path to an ISAPI executable file is specified, returns all dependencies on the specified file.
Example	This example returns the ISAPI module dependencies on an IIS 6.0 Web server. msdeploy -verb:getDependencies,isapi -source:webServer60

Setting	managedType
Usage	-verb:getDependencies,managedType -verb:getDependencies,managedType=< managedType >
Description	Returns the names of all applications that depend on managed types. When the file path to a managed type is specified, returns all dependencies on the specified managed type.
Example	This example returns the managed type dependencies on an IIS 7 Web server. msdeploy -verb:getDependencies,managedtype -source:webServer

Setting	nativeModule
Usage	-verb:getDependencies,nativeModule -verb:getDependencies,nativeModule=<nativeModuleFilePath>
Description	Returns the names of all applications that depend on native modules. When the file path to a native module is specified, returns all dependencies on the specified native module.
Example	This example returns the native module dependencies on an IIS 7 Web server. msdeploy -verb:getDependencies,nativemodule -source:webServer

Setting	noTrigger
Usage	-verb:getDependencies,notrigger
Description	Specifies that no trigger elements will be returned. This is the default Web Deploy behavior for getDependencies when no setting is specified. For more information about trigger information, see Controlling the Output of Trigger Information.
Example	This example returns the names of the application pools in use on an IIS 6.0 Web server. Because the notrigger setting has been specified, the paths to the Web sites that are using each application pool will not be displayed. msdeploy -verb:getDependencies,appPoolInUse,notrigger -source:metakey=lm/w3svc/1

   

Note

You can obtain a list of installed IIS components by using the getSystemInfo operation, which gathers IIS-related system information. For more information, see Web Deploy GetSystemInfo Operation.

Example Usages

1) Return the dependencies for an IIS 6.0 root Web application.

msdeploy -verb:getDependencies -source:metaKey=lm/w3svc/1/root

2) For the specified metabase key, return all dependencies on Windows authentication or application pools that are being used.

msdeploy -verb:getdependencies,dependency=windowsauthentication,apppoolinuse -source:metaKey=lm/w3svc

3) From an IIS 6.0 Web server, return all dependencies on ASP.NET 1.1 or application pools that are being used.

msdeploy -verb:getDependencies,dependency=aspnet1.1,apppoolInUse -source:metakey=lm/w3svc

4) Return the native module dependencies from an IIS 7 Web server.

msdeploy -verb:getDependencies,nativeModule -source:webServer

See Also

Controlling the Output of Trigger Information

How Dependencies are Determined

Viewing Dependencies

Web Deploy GetSystemInfo Operation

Web Deploy Operations

Web Deploy Rules