Examples using the command line

This topic provides some simple examples of how to use the command line interface.

Analyzing an assembly for exceptions

To detect the exceptions for all methods in the assembly WidgetAssembly.dll :

hunt /assembly:WidgetAssembly.dll 

     /all

If you do not specify the path to the assembly file, Exception Hunter assumes it is in the same folder as the Hunt.exe file. To specify an assembly in a different folder, enclose the full path in quotes:

hunt /assembly:"C:\MyProjects\WidgetProject\WidgetAssembly.dll" 

     /all

Note: If you do not specify either /all or at least one method using the /method argument, an error is returned.

Analyzing more than one assembly

To analyze more than one assembly, use separate /assembly arguments to specify each assembly:

hunt /assembly:"C:\MyProjects\WidgetProject\WidgetAssembly1.dll"

     /assembly:"C:\MyProjects\WidgetProject\WidgetAssembly2.dll"

     /assembly:"C:\MyProjects\WidgetProject\WidgetAssembly3.dll"

     /all

Selecting specific methods to analyze

To specify particular methods to analyze, use the /method argument. Use a separate argument for each method:

hunt /assembly:"C:\MyProjects\WidgetProject\WidgetAssembly1.dll"

     /method:System.Int32.ToString(String)

     /method:System.Code.WidgetFunction()

You need to specify only enough of the name to make it unique.

Producing a report

By default the results of the analysis are output to the console.

Use the /xml switch to produce a results file containing the results as a set of xml data that you can translate into whatever format you require. You can also choose one of two HTML format reports:

• /methodReport

  The results are organized by method.

• /exceptionReport

  The results are organized by exception type.

Setting analysis options

Use the following switches to control how Exception Hunter analyzes your methods:

For a complete list of arguments and syntax for the command line, type:

hunt /? /v