TeamCity
 
You are viewing the documentation for an earlier version of TeamCity.

Inspections (.NET)

Last modified: 20 April 2023

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. Usage of the tools within TeamCity does not require any additional licensing for ReSharper. 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

If you want to run ReSharper inspections using a specific ReSharper version (e.g. to ensure it matches the version you have installed in Visual Studio), since TeamCity 10.0 you can install another version of the tools and can change the default version to be used using the Administration | Tools page.

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

You can also refer to ReSharper documentation for more details.

Sources to Analyze



Environment Requirements



InspectCode Options



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.