Command Line

In order to use ReSharperReports, the following inputs are using:

Required Parameters

• InputFilePath
  • -i, --inputFilePath: The path to the input report XML to be transformed.
• OutputFilePath
  • -o, --outputFilePath: The path to the output report in HTML format.

Optional Parameters

• XslFilePath
  • -x, --xslFilePath: The path to the input XSL file to be used to perform transformation.
• LogFilePath
  • -l, --logFilePath: Path to where log file should be created. Defaults to logging to the console.
• Version
  • --version: Outputs the current version number of the ReSharperReports tool
• Help
  • --help: Provides help documentation for how to run ReSharperReports

Example Usage

The following is an example of how to transform the report generated by DupFinder:

NOTE: ReSharperReports will auto-detect whether the provided report comes from DupFinder or InspectCode and use the correct default XSL Transformation file.

ReSharperReports.exe transform -i "c:/temp/dupfinder-output.xml" -o "c:/temp/dupfinder-output.html"

The following is an example of how to transform the report generated by InspectCode:

ReSharperReports.exe transform -i "c:/temp/inspectcode-output.xml" -o "c:/temp/inspectcode-output.html"

If you want to override the default XSL Transformation, and provide your own transformation file, you would use the following:

ReSharperReports.exe transform -i "c:/temp/dupfinder-output.xml" -o "c:/temp/dupfinder-output.html -x "c:/temp/inspectcode.xsl"

To pipe the generated log messages to a separate file, you would use the following:

ReSharperReports.exe transform -i "c:/temp/dupfinder-output.xml" -o "c:/temp/dupfinder-output.html -l "c:/temp/resharperreports.log"