When to use a Field vs a Property

I would not expect that you could access a private field from a derived class! But fields should only be private, and properties should use when access is to be allowed outside of the class.

For other info about using fields vs. properties, see the MDN Design Guidelines for Field Design and Property Design.

Steven let me ask the question in a different manner.

While creating class hierarchy what is the preferred way to defining the attributes being used by the derived classes:

For ex:

Approach 1:

public abstract class BaseController: Controller
{
    protected Context _context = null;
    public BaseController()
    {
        _context = new Context();
    }

}

Approach 2:

public abstract class BaseController: Controller
{
    protected Context Context {get; set;};
    public BaseController()
    {
        Context = new Context();
    }

}

I have implemented the logic both ways and its produces expected results. So the question is when to use which one and why?

Is this what should be followed: fields should only be private, and properties should use when access is to be allowed outside of the class.

Thanks Steven