Cause

A type has a disposable field (a field that implements IDisposable). This field is being assigned on the type construction by constructing a new object. It is very likely that the enclosing type owns the object and should then dispose it, implementing IDisposible itself (if it does not yet implement yet).

Example

Assuming class D implements IDisposable:

class TypeName
{
    private D field = new D();
}

Code fix

A code fix will be presented to you that will transform the code, it will implement IDisposable if the type has not implemented it yet, and add a call do Dispose on the field.

class TypeName : System.IDisposable
{
    private D field = new D();

    public void Dispose()
    {
        field.Dispose();
    }
}

Related rules

• CC0022 - Disposable variable not disposed
• CC0029 - Disposable should call SuppressFinalize
• CC0032 - same rule, but field is being assigned by a method call

See also

TBD