In this section:
The command-line is the primary interface for running dotTEST in a non-interactive mode. The interface allows you to run dotTEST from any other script, language or build system that can launch a program, including
*.cmd scripts. For MSBuild, NAnt, or JetBrains TeamCity, use the integrators shipped with dotTEST (see Integrations).
Analyzing Visual Studio Solutions
Provide the paths of a solution to analyze code. The following versions of Visual Studio solutions can be analyzed: 2012, 2013, 2015, 2017.
Analyzing a Single FileSolution
-solution switch to specify path of the solution. For example, you command line may resemble the following:
Analyzing Multiple Solutions
-solution switch multiple times or provide ANT-style wildcards. For example, you command line may resemble the following:
Analyzing Visual Studio Projects Without Solutions
You can specify a path or paths to
*.vbproj projects if
*.sln files are unavailable by using the
-project switch. The
-solution switch is recommended, however, and should be used whenever possible.
ANT-style paths are supported. The switch may be specified several times.
Visual Studio Web Site projects do not use
*.*proj files and may be maintained without
*.sln files. Use the
-website switch to specify the directory of the website when no
*.sln files are present. For example, you command line may resemble the following: