StyleCopAnalyzers

I think there are also a lot of default rules which aren't enforced until they're bumped up in severity in the .editorconfig. Also it can hook into roslyn analyzers, so if you want a more opinionated analyzer then stylecop analyzers ( https://github.com/DotNetAnalyzers/StyleCopAnalyzers) would be an option, although I haven't used it myself for a long time.

It’s actually /// (3 slashes) that reserved for pseudo-documentation use. There’s a StyleCop rule to enforce this as well: https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/ma...

Here’s more about commenting style: https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/ma... StyleCop is used for analyzing code style in C# code. Specifically: > If the comment is being used to comment out a line of code, begin the comment with four forward slashes rather than two. StyleCop relies on this to tell the difference between commented code and code comments. If you use ReSharper, it can do some nifty transformation to strike these out in the IDE which is kinda cool too. I’m a big fan of StyleCop to enforce consistent code styles. (Even if it’s not always what I may aesthetically prefer.)

As a user/consumer of (various) open source projects - I can accept that they change/die/merge/etc over time. A lot of time it is volunteer time and priorities changes. With that in mind...how can you properly communicate a transition from a current project to another? StyleCop would be a helpful example here. The current version appears (or at least seems to be) dead and/or dying [1]. It has been cloned to github [2] (from codeplex) but nobody is making an effort. I would be willing _but_ after further research I found out that in fact it is sort of rising as a re-implementation with all the Microsoft open sourcing [3]. Which is really great...except the effort of finding this out wasn't exactly easy for me and I was pretty interested in finding out what was going on. It seems like this is sort of the middle ground of one still being val