The tool takes an msbuild binlog and looks for illink invocations. It picks one (based on options) and create a repro directory to be abel to run the same illink separately. This means:
- Rewrite the command line for the tool to a new .rsp file
- Copy all input files into the
inputdirectory - Redirect output to
outdirectory - Rewrite command line to point to the
inputdirectory using relative paths only
Ideally the repro directory can be zipped and moved to a different machine and be able to repro the illink invocation exactly.
Typical use:
illinkrepro create msbuild.binlog
This will find the only illink invocation which failed and create a repro for it in the repro subdirectory of the current directory.
Common command line options:
-o <path>- specifies the output directory for the repro. Can be a relative path to the current directory.-f- force overwrite the repro directory. Otherwise if the directory already exists the tool will fail.--project <project name>- useful if there are multiple projects using illink in the binlog. Specify the name of the project for which the repro should be created.
If you're planning to share the repro with others (or even publicly), please be aware that the repro directory will contain all of the compiled assemblies of your application (.dll) and all of trimmer command line customizations. Make sure that these don't contain information you don't want to share.