Browse by term
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.
Why applying one uniform static-analysis ruleset to both production and test code serves neither well, and what a more relaxed ruleset for tests actually buys a team.
Why brownfield and greenfield code call for different static-analysis rulesets, and how that split turns modernization into an incremental, sustainable process instead of a single risky migration.
The two common conventions for ordering C# using directives, how ReSharper, Rider, StyleCop, Visual Studio, and .editorconfig each support them, and the specific settings that control the behavior.
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 DevTree folder structure for separating experimental trials, spikes, samples, prototypes, and clean production code according to their purpose and maturity.
How to make ReSharper understand .NET Code Contracts such as Contract.Requires by extending its external annotations and eliminating false nullability warnings.
How to suppress FxCop and Code Analysis warnings such as CA1811 and CA1812 in ArcGIS Desktop 10 Add-In code generated by ArcGISAddInHostGenerator.
A summary of .NET event naming guidelines and conventions for event handlers, EventArgs classes, pre- and post-events, and overridable OnXxx methods.
How to automate NUnit tests with consistent naming, a Windows batch runner, test categories, XML result files, and Hudson CI test reporting.
How to obtain and install a newer FxCop release from the Windows SDK for Windows 7 and .NET Framework 4 when the FxCop GUI update link is broken.
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 use a project-specific FxCop custom dictionary with Visual Studio Code Analysis by linking the dictionary into each project and configuring CodeAnalysisDictionary in the csproj file.
Fixing a Code Analysis/FxCop error in mixed VS2005/VS2008 projects by pointing the VS2005 targets at the VS2008 FxCop binaries.
How to configure StyleCop SA1600 documentation warnings to ignore missing documentation
How to make a custom FxCop dictionary available to Visual Studio.
How to integrate Microsoft FxCop into Visual Studio builds using post-build events
Performancevergleich von as, is und direkten Casts in C#
C#-Tipps für ArcObjects: unnötige doppelte Casts mit is und explizitem Cast vermeiden sowie Next()-Schleifen kompakter und verständlicher formulieren.