C# |

A set of Roslyn Analyzer aimed to enforce design and cybersecurity best practices, as well as code quality (QA) rules.
https://github.com/DogmaSolutions/Analyzers

Recent commits:

feat(dsa045): report a type with logic that is excluded from the code coverageDSA045 only checked one direction: a pure data carrier that is not excluded.It now checks the opposite one too: a type that has logic and is decoratedwith [ExcludeFromCodeCoverage] hides from the coverage figure code that canbreak and that nobody is pushed to test.The message names the first piece of logic found, and the code fix removesthe attribute from every part of the type, keeping the other attributes, thedocumentation and the indentation. Only the members of the type itself areinspected, and only an attribute on the type itself is reported. The optionreport_excluded_types_with_logic (default true) turns the scenario off.Refs: #28, Dogma Solutions
fix(dsa051): the default severity is suggestionThe rule fires on every class without a ToString(): it is shown in the IDE,and it is a suggestion in the three recommended profiles as well.Refs: #28, Dogma Solutions
fix: state the type and the platforms that each message is true forDSA010 said that a single read or write is atomic without saying for whichtype nor on which platforms. The messages now name the type of the field andsay what the CLR guarantees for it: one indivisible operation on everyplatform for types of 32 bits or less and for references, only in a 64-bitprocess for long, ulong and double, and on no platform for decimal and structs.The alternatives to the lock name the Interlocked overloads that exist for thetype.The same accuracy for the other rules that depend on the type or on theframework: DSA046 names the Interlocked methods that exist for the type of thefield and the framework that has them, and its code fix no longer offers theunsigned overloads where the framework does not have them; DSA037, DSA038 andDSA039 say from which .NET version Random.Shared andRandomNumberGenerator.GetInt32 are available, and that the parameterlessRandom constructor is clock-seeded on .NET Framework.The review comment test of DSA051 no longer depends on the line endings of thesource file.Refs: #28, Dogma Solutions
feat: added DSA051, a class without a ToString() overrideThe analyzer reports a class (or, on request, a struct) that neither declaresnor inherits a ToString(): in the debugger, in logs and in failed assertions aninstance shows up as its type name only.The code fix generates the override, from the first member of a configurablelist of well known names (Id, Name, Email…), else from all the publicproperties, else the protected ones, else the fields. Members whose name lookslike a secret are never written. Nothing is generated for a type withoutproperties and fields.Refs: #28, Dogma Solutions
fix(dsa019): offer the extraction of the shared prefix even when the whole chain cannot be extractedThe extraction of the common root was registered only inside the branch thatoffers the extraction of the chain itself. When the first use of the chain sitsbehind a check on its prefix, the chain is rightly not extracted, but theprefix is the first thing the check reads and can be, so no fix was offered.Refs: #28, Dogma Solutions

Federico Coletto

No, I won't fix your computer

Category Archives: C#

.NET 8 Quality Assurance coding rules and best practices

ASP.NET 5 Quality Assurance coding rules and best practices

.NET 6 Quality Assurance coding rules and best practices

Change Impact Analyzer

.NET 5 Quality Assurance coding rules and best practices

ASP.NET 6 Quality Assurance coding rules and best practices

Dogma Solutions Roslyn Analyzers