Controlling the Output of Trigger Information
Applies To: Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, Windows Vista, Windows XP
When no settings are specified for getDependencies, the default behavior is for no trigger information to be returned. When a feature-specific setting is used with getDependencies, the default behavior is for all trigger information to be returned. You can override these defaults by using the alltrigger and notrigger settings. The following table shows these default behaviors and how you can override them by using alltrigger and notrigger.
| getDependencies command | Result | ||
|---|---|---|---|
|
No trigger information is returned (notrigger is the default). |
||
|
All trigger information is returned (the alltrigger setting overrides the notrigger default).
|
||
|
All trigger information is returned for the specified dependency (alltrigger is the default). |
||
|
No trigger information is returned for the specified dependency (the notrigger setting overrides the alltrigger default). |
.gif)
NoteReducing trigger information
If you use the alltrigger setting, all dependencies and trigger information from the source that you specify will be returned. To reduce the verbosity of this output, use one of the feature-specific appPoolInUse, cgi, dependency, isapi, managedType, or nativeModule settings. By reducing the scope of the operation, you will reduce the amount of information returned. The following example specifies that only ISAPI dependencies be returned from an IIS 6.0 Web server. The sample output is shown.
msdeploy -verb:getDependencies,isapi -source:webServer60
Sample output
<dependencyInfo>
<isapis>
<isapi dll="C:\WINNT\system32\inetsrv\httpodbc.dll" enabled="False">
<trigger absolutePath="/LM/W3SVC/ScriptMaps" />
</isapi>
</isapis>
</dependencyInfo>
See Also
How Dependencies are Determined