Skip to end of metadata
Go to start of metadata

The Duplicates Finder (.NET) Build Runner based on ReSharper Command Line Tools is intended for catching similar code fragments and providing a report on discovered repetitive blocks of C# and Visual Basic .NET code in Visual Studio 2003, 2005, 2008, 2010, 2012, 2013, and 2015 solutions.

TeamCity comes bundled with JetBrains ReSharper Command Line Tools, and since TeamCity 10.0, in addition to the bundled version, it is possible to install another version of the tools and/or change the defaults using the Administration | Tools page.

Icon

This runner requires .NET Framework 4.0 (or higher) to be installed on the agent where builds will run.

This page contains reference information about the following Duplicates Finder (.Net) Build Runner fields:

Sources

Option

Description

Include

Use newline-delimited Ant-like wildcards relative to the checkout root to specify the files to be included into the duplicates search.
Visual Studio solution files are parsed and replaced by all source files from all projects within a solution.
Example: src\MySolution.sln

Exclude

Enter newline-delimited Ant-like wildcards to exclude files from the duplicates search (for example, */generated{*}{}.cs). The entries should be relative to the checkout root.

Duplicate Searcher Settings

Option

Description

Code fragments comparison

Use these options to define which elements of the source code should be discarded when searching for repetitive code fragments. Code fragments can be considered duplicated, if they are structurally similar, but contain different variables, fields, methods, types or literals. Refer to the samples below:

Discard namespaces

If this option is checked, similar contents with different namespace specifications will be recognized as duplicates.

Discard literals

If this option is checked, similar lines of code with different literals will be recognized as duplicates.

Discard local variables

If this option is checked, similar code fragments with different local variable names will be recognized as duplicates.

Discard class fields name

If this option is checked, the similar code fragments with different field names will be recognized as duplicates.

Discard types

If this option is checked, similar content with different type names will be recognized as duplicates. These include all possible type references (as shown below):

Ignore duplicates with complexity lower than

Use this field to specify the lowest level of complexity of code blocks to be taken into consideration when detecting duplicates.

Skip files by opening comment

Enter newline-delimited keywords to exclude files that contain the keyword in the file's opening comments from the duplicates search.

Skip regions by message substring

Enter newline-delimited keywords that exclude regions that contain the keyword in the message substring from the duplicates search. Entering "generated code", for example, will skip regions containing "Windows Form Designer generated code".

Enable debug output

Check this option to include debug messages in the build log and publish the file with additional logs (dotnet-tools-dupfinder.log) as an artifact.