Hi .NET folks

We’ve all felt the pain of deadlocks so now SonarSource has a new rule for C# and VB.NET that can detect when a resource has been locked and might not get released. It’s the first rule to benefit from our new Symbolic Analysis engine and we’re pretty excited about it. It’s been enabled in the default SonarWay profile so look out for new issues and let us know if you’re finding it useful. In future releases, as more rules use the new engine, you’ll see improved accuracy and better support for the latest language features.

The rule is available in SonarCloud today and will follow in SonarQube 9.5 and SonarLint soon.

That is a nice addition. It might be worth to add another rule in this erea:

private object lock = new object(); // Noncompliant {{lock objects should be read-only.}}
Compliant
private readonly object lock = new object();
    
As proposed by @Corniel here: https://community.sonarsource.com/t/new-rule-for-c…-and-vb-net-locks-should-be-released/60951/2
### Non-compliant
private object lock = new object(); // Noncompliant {{lock objects should be read-only.}}
### Compliant
private readonly object lock = new object();
    How to Report a False-positive / False-negative Report False-positive / False-negative...
    Hey SonarSource Community! 
False-positives happen, as do false-negatives, and we’re eager to fix them. We are thrilled when our users report problems, so we can make our products better. 
What is a false-positive (FP)?
A false-positive is when an issue is raised unexpectedly on code that should not trigger an issue, or where the suggested action doesn’t make any sense for the code. 
What is a false-negative (FN)?
A false-negative is when an issue should be raised on a piece of code, but isn’t.