...
-solution"C:\Devel\FooSolution\FooSolution.sln"-solutionConfig Debug -targetPlatform "Any CPU"-project"C:\Devel\FooSolution\FooProject.csproj"-projectConfig Debug -targetPlatform AnyCPU
Anchor resource resource
-resource <path relative to the solution>
...
-exclude"C:/Devel/FooSolution/*.Tests/**/*.*"-include "C:/ProductX/Solution1/src"
Alternatively, you can specify a list of patterns in a .lst file and pass the file with the -include or -exclude switch. Each line in the file will be treated as a single entry.
-reference <path>
This setting specifies the path to aditional assemblies needed to resolve dependencies of the analyzed projects. Use this option if you receive an "Unable to find reference assembly" message. You can use Ant-style wildcards and relative paths to the current working directory. Example:
-reference C:\MySolution\ExternalAssemblies\*.dll-reference C:\Solution1\Assemblies2018\*.exe-reference C:\FooSolution\Ext\**\*.dll
See .Configuring+the+Test+Scope+v10.4.0 for details.
Reporting
-report <path>
This option specifies the path to the directory where the report will be created.
...
Customizing Configuration
-settings <path>
This option specifies the path to a custom .properties file that includes customized settings in the following format: key=value (for example, report.format=pdf). You can use this option multiple times to specify several .properties files. Entries with the same key will be overwritten. Example:
-settings Project1Config.properties
...
This option allows you to configures configure a single setting directly in the command line. Use the following format: key=value.
You can use this optoin option multiple times to configure several settings on the came same command line. Earlier entries with the same key will be overwritten. Examples:
...