[.NET@Noon] Don't Make Me Repeat Myself: Analyzers & More For Quality by Default
Details
We all have coding rules and conventions for our projects. Typically, these live in the heads of the team, and sometimes just whoever has been there the longest. That means they often don't get enforced until it's time for a pull request.
Unfortunately, this doesn't scale too well, and can be quite annoying, to boot! Enforcement depends on the right reviewer seeing your pull request at the right time, and it can feel like an uphill battle to even keep your project's code up to your own standards.
Thankfully, most rules and conventions we want to use can actually be enforced as something that fails the build. This session will show you how and why to use tools like Roslyn analyzers, architecture tests, and classic code formatters to enforce at build time the rules your team cares about.
