Build, Scripts, Resources within the Resharper toolbar > Options > Code Inspection > Settings section Tip Exclude folders which contain third-party or generated code e.g. Some recommendations: Code issueĪuto-property accessor is never used (non-private accessibility) Optional improvements should be set as Suggestion or Hint in the team-shared rules to prevent unnecessary build failure. Tip The build is configured by default to fail at the Warning level. Commit the changed sln.DotSettings file and the next build will use the updated rules. To customize the rules, it is possible to manage the team-shared options in the Inspection Severity section from the Resharper toolbar within Visual Studio. The CLT will use the default code quality inspections to generate a report with no Resharper or Visual Studio license necessary. task: 'Build Target ($(Build.Target))'Īrguments: '-configuration $(Build.Configuration)'ĪdditionalArguments: '/disable-settings-layers:SolutionPersonal -properties:Configuration=$(Build.Configuration)' VmImage: 'windows-2019' # note that the Resharper CLT will only work on a windows machine or container Yaml Pipeline Sample name: 'Sample Code Quality Job'

Net Core 3 projects using the Yaml pipeline sample for best results Net Framework projects with the VS 2017 hosted agent for best results

Set the path to your solution (.sln) or project (.csproj) file.

Add the Resharper Code Quality Analysis task to your build template.

Add this task to your continuous build to fail the build whenever code quality standards are violated. Based on the free-to-use Resharper Command-Line Tools (CLT), this build task will automatically run over a thousand code quality checks for various languages including C# and Typescript.

Download resharper c#