API

Avoid empty catch sections

Docs > Code Analysis > Static Analysis Rules > Avoid empty catch sections

Metadata

ID: csharp-best-practices/no-empty-catch

Language: C#

Severity: Warning

Category: Best Practices

Description

Exceptions must be appropriately handled and have code to recover from the exceptions. If no recovery is added, the code should at least log the error.

Non-Compliant Code Examples

class MyClass {
    public static void routine()
    {
        try {
            doSomething();
        } catch (MyException ex) {
            
        }
    }
}

class MyClass {
    public static void routine()
    {
        try {
            doSomething();
        } catch (MyException ex) {
            // comment
        }
    }
}

Compliant Code Examples

class MyClass {
    public static void routine()
    {
        try {
            doSomething();
        } catch (MyException ex) {
            handleException();
        }
    }
}

How to use this rule

1
2
rulesets:
  - csharp-best-practices     # Rules to enforce C# best practices.

Create a static-analysis.datadog.yml with the content above at the root of your repository
Use our free IDE Plugins or add Code Analysis scans to your CI pipelines
Get feedback on your code

For more information, please read the Code Analysis documentation

VS Code Extension

Identify code vulnerabilities directly in your
VS Code editor

JetBrains Plugin

Identify code vulnerabilities directly in
JetBrains products