When should you call base.Method() in overridden method, and how to mark this when you write code in team?

Question

When using some framework/api, sometimes it\'s pretty unclear if you must call base.Method if you override it, for example you can be pretty sure that you should call base.M

Answer 1

It depends on whether the underlying functionality needs to be used.

For example, if the base object has some generic database functionality that needs to be run, call the base method at the end. If your code overwrites some of the properties that the base method will set, rather call the base method first.

If there is no source code or documentation, RedGate's .Net Reflector (http://www.red-gate.com/products/dotnet-development/reflector/) can just unpack the assemblies you are trying to use and you can see how the code works.

Answer 2

Nowadays I don't think that consumers of a class that override a method should ever need to call base.Method(). The code should be written in such way that it cannot be broken.

public class MyBase
{
    private void FooInternal()
    {
        DoRequiredStuff();
        Foo();
    }
    public virtual void Foo() {}
}

Answer 3

If you are requiring that consumers of your class MUST implement functionality of a particular method, that method should be marked abstract.

If consumers of your class should optionally provide functionality of a particular method, that method should be virtual.

There is really no way to require that a consumer of a class call a base.Method() on a virtual method. It really depends on context. If the base.Method() does some work that you'd otherwise have to do, it'd behoove you to call base.Method() if that would save you some development time/it makes sense in that context.