C
C#9mo ago
Bill

❔ Analyzers Project

Hello, I've added an Analyzers project with the following NuGet packages (in the file) that I found from https://github.com/cybermaxs/awesome-analyzers?tab=readme-ov-file and then referenced this project on all of my others. My question is, is this overkill are you just okay with the following:
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>latest</AnalysisLevel>
<EnforceCodeStyleInBuild>true</EnforceCodeStyleInBuild>
<AnalysisMode>Recommended</AnalysisMode>
<EnableNETAnalyzers>true</EnableNETAnalyzers>
<AnalysisLevel>latest</AnalysisLevel>
<EnforceCodeStyleInBuild>true</EnforceCodeStyleInBuild>
<AnalysisMode>Recommended</AnalysisMode>
I'm trying to help my team build the highest quality code possible
GitHub
GitHub - cybermaxs/awesome-analyzers: A curated list of .NET Compil...
A curated list of .NET Compiler Platform (&quot;Roslyn&quot;) diagnostic analyzers and code fixes. Everyone can contribute here! - GitHub - cybermaxs/awesome-analyzers: A curated list of .N...
4 Replies
Murten
Murten9mo ago
Maybe just ask your team what they think. worryshrug
JakenVeina
JakenVeina9mo ago
as long as none of those analyzers are trying to enforce styling or formatting, I'd say go for it, with input from your team in my mind, it'd be best to go aggressive with analyzers, and then pull back as needed you ought to be able to disable any of the individual analyzer warnings/errors at any point in the future maybe have a standing agenda item in weekly meetings or whatever for "Hey, are there any analyzer warnings we should turn off?"
Bill
Bill9mo ago
Great solution, that’s what I’m going to go with. Thank you This post is to more so to make sure I’m not overdoing it based on best practices. I have a ton of analyzers in the project
Accord
Accord9mo ago
Was this issue resolved? If so, run /close - otherwise I will mark this as stale and this post will be archived until there is new activity.