Wiring Up Static Code Analysis via Directory.Build.props
A concrete Directory.Build.props example that incorporates Microsoft's .NET analyzers and StyleCop Analyzers, and applies stricter analysis to production projects than to tests and tooling.
Browse by term
A concrete Directory.Build.props example that incorporates Microsoft's .NET analyzers and StyleCop Analyzers, and applies stricter analysis to production projects than to tests and tooling.
How a cross-team rule set for .NET static code analysis splits responsibilities between Microsoft's analyzers and StyleCop, and why production and non-production code get deliberately different strictness levels.
A balanced look at #region in C# — where it genuinely helps navigate large files, and where it just hides code that needs refactoring.
How to run StyleCop on a minimal Continuous Integration server without installing it by storing the required assemblies and MSBuild target in the project's DevTree.
A collection of StyleCop and FxCop SuppressMessage examples for common code analysis issues, including naming, IoC, testing, exceptions, documentation, strong names, and framework-specific cases.
How to configure StyleCop SA1600 documentation warnings to ignore missing documentation
Installing StyleCop for ReSharper under an administrative account does not activate this ReSharper plugin under my developer account.
How to fix MSB3073 errors in Visual Studio post-build events by quoting macros such as $(TargetPath) when file or folder paths contain spaces.