The console application gives you a command-line interface from which you can run a comparison and generate reports.

The console application has two modes of operation: Use an existing comparison set (.cset) file, or pass all information in through the command line.

To use this option, first run the BitDiffer GUI application and create and configure your comparison files/directories, options, and view filters. Then save the set to a BitDiffer .cset file.

To execute the comparison from the command line, simply pass the .cset file name to the BitDiffer command line:

BitDiffer.Console.exe -out "report.html" "file.cset"

You can also run the BitDiffer console and specify the complete set of options on the command line:

BitDiffer.Console.exe [options] "file1" "file2" ... "fileN"

-dirs Compare directories: Inputs files are directory names

-out "report.html" Output comparison report to specified file (.HTML or .XML)

-raw "details.xml" Output raw details to given file

For a description of these options, refer to the topic View Filters.

-all Report all items instead of just changed items

-publiconly Only compare exported (public) types and members

-noimpl Do not compare method and property implementations

-noattrs Ignore changes in assembly attributes

For a description of these options, refer to the topic Configuration Options.

-nomulti Do not multithread

-gacfirst Try to resolve references from the GAC first

-isolation level Set isolation level. Valid values are "low", "medium" or "high". (Use with caution)

-execution Load into execution context rather than reflection context

Compare public types of three assemblies and output results to an HTML report:

BitDiffer.Console.exe -publiconly -out "report.html" "C:\Temp\Assembly1.dll" "C:\Temp\Assembly2.dll" "C:\Temp\Assembly3.dll"

Compare all assemblies in three directories (ignore method implementations) and output results to an XML report:

BitDiffer.Console.exe -noimpl -out "report.xml" "C:\Temp1" "C:\Temp2" "C:\Temp3"