c# - Public readonly field v.s. get-only property

Question

Are there cases when you would want a public readonly field v.s. a get-only auto-implemented property?

public class Foo
{
    public readonly string Hello;

    public string Hello2 { get; }
}

Both can only be set during the constructor and both offer readonly access outside of the class.. I'm a little tired so I might be missing something.

Answer 1

Making it a property rather than a field means it can be used on interfaces.

The exact implementation (although auto-properties don't really have much implementation...) is also abstracted, so you could in the future base it on a combination of fields without breaking (compile) compatibility.