Why you shouldn't call GC.SuppressFinalize(this) unless you directly have a finalizer

nosuppress.cs

public class MyClass : MyDerivedClass {
    public override void Dispose() {
        base.Dispose();
        GC.SuppressFinalize(this); // here we improperly call GC.SuppressFinalize(this)
    }
}

public class MyDerivedClass : MyBaseClass {
    public override void Dispose() {
        ; // oops, we forgot to call base.Dispose();
    }
}

public class MyBaseClass : IDisposable {
    public virtual void Dispose() {
        // here we properly call GC.SuppressFinalize because we have a finalizer
        GC.SuppressFinalize(this);
        // but this dispose method will never get called
    }

    ~MyBaseClass() {
        ; // and this finalize will never run now because MyClass.Dispose suppressed it :(
    }
}

// Overall, the benefit to calling GC.SuppressFinalize in the derived class is neglible if
// somehow the base class didn't do it, but the drawback to doing it when you don't own the
// unmanaged resource protected by the finalizer could be huge.