Skip to end of metadata
Go to start of metadata

The Inspections (.NET) runner allows you to use the benefits of JetBrains ReSharper code quality analysis feature right in TeamCity using the bundled JetBrains ReSharper Command Line Tools. 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.

ReSharper analyzes your C#, VB.NET, XAML, XML, ASP.NET, ASP.NET MVC, JavaScript, HTML, CSS code and allows you to:

  • Find probable bugs
  • Eliminate errors and code smells
  • Detect performance issues
  • Improve the code structure and maintainability
  • Ensure the code conforms to guidelines, standards and specifications

This page contains reference information about the Inspections (.Net) Build Runner fields:

You can also refer to ReSharper documentation for more details.

Icon

To run inspections for your project, you must have a ReSharper inspection profile for .NET projects.

Sources to Analyze

Option

Description

Solution file path

The path to .sln file created by Microsoft Visual Studio 2005 or later.
The specified path should be relative to the checkout directory.

Projects filter

Specify project name wildcards to analyze only a part of the solution. Leave blank to analyze the whole solution.
Separate wildcards with new lines.
Example:

Environment Requirements

Icon

In order to launch inspection analysis, you should have .NET Framework 4.0 (or higher) installed on an agent where builds will run.

Option

Description

Target Frameworks

This option allows you to handle the Visual Studio Multi-Targeting feature.
Agent requirement will be created for every checked item.

Icon

.NET Frameworks client profiles are not supported as target frameworks

InspectCode Options

 

Option

Description

Custom settings profile path

The path to the file containing ReSharper settings created with JetBrains Resharper 6.1 or later.
The specified path should be relative to the checkout directory.
If specified, this settings layer has the top priority, so it overrides ReSharper build-in settings. By default, build-in ReSharper settings layers are applied.
For additional information about ReSharper settings system, visit ReSharper Web Help and JetBrains .NET Tools Blog

Enable debug output

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

Additional inspectCode.exe arguments:

Specify newline-separated command line parameters to add to calling inspectCode.exe.

Icon

To get the output xml report from Inspections (.NET) Runner, specify the path to the output file here via the -o or –output additional command line arguments. The paths relative to the build checkout directory as well as absolute paths are supported.

Build Failure Conditions

If a build has too many inspection errors or warnings, you can configure it to fail by setting a build failure condition.

Build before analyze

In order to have adequate inspections execution results, you may need to build your solution before running analysis.
This pre-step is especially actual when you use (implicitly or explicitly) code generation in your project.

  • No labels

1 Comment

  1. If you want to set C# language level (e.g. if you do not use C# 6 features in the project), this can be done in a single place.