HighFile-scopeC# Plug & play

Avoid Empty Finalizers

Check that finalizers are not left empty. If cleanup is needed, ensure proper resource disposal is implemented instead.

Why this matters

Empty finalizers introduce unnecessary performance overhead. If cleanup is needed, implement proper resource disposal instead.

Side-by-side examples engineers can pattern-match during review.

Avoid

public class Foo
{
    ~Foo() // Noncompliant
    {
    }
}

Prefer

// (no example provided)

Bad

public class Foo
{
    ~Foo() // Noncompliant
    {
    }
}

From the same buckets as this rule.

Critical
Avoid Duplicating String Literals
Store repeated string literals in constants or variables to improve maintainability and reduce redundancy.
duplication-complexitymaintainability
Critical
Avoid Empty Methods
Detect methods that have an empty body. If a method is empty, ensure that a comment is present explaining why it remains unimplemented.
maintainabilityreadability-refactor
Critical
Avoid modifying built-in prototypes
Detect modifications to built-in prototypes. Modifying built-in objects can lead to compatibility issues and unexpected behavior. Recommend creating helper functions instead.
maintainabilitysecurity-hardening