Should we assess .NET project using the IDEs built in tool?

[booyaa]

To give a tangible example, I'm currently using JetBrains Rider to evaluate a project. JetBrains Rider has built-in Linter (called Code Inspectors), Code Coverage (via plugin) and Profiling (Debugger).

My initial feeling is to say that that we should find tools to do separately for the sake of continuous delivery pipelines.

We've discussed this internally on our slack and there have been no definitive answers.

cc @StevenLeighton21 @robinlacey (please ping others who may be interested in this discussion)

[davidwinter]

I think we should be able to use these tools locally, but also, that it's essential that the pipeline does these things to act as our gatekeeper to production.

[craigjbass]

Most .NET devs follow Microsoft standards (resharper and rider are configured to pick this up and provide quick fixes.

To keep things simple, it makes sense to me to follow this unless we can see any harm

https://github.com/quozd/awesome-dotnet/blob/master/README.md#code-analysis-and-metrics

Some good tooling here

[craigjbass]

Could investigate this https://sonarcloud.io/about/sq

[booyaa]

I've started trialling StyleCop, needs fine tuning and further discussion as to what rules are enabled by default.