Why use private members then use public properties to set them?

Question

Seen a few examples of code where this happens:

public class Foo
{
    string[] m_workID;
    public string[] WorkID
    {
        get
        {
                     


        

Answer 1

You can use C# 3.0 auto properties feature to save time typing:

public class Foo
{
    public string[] WorkID
    {
        get; private set;
    }
}

In addition properties gives you lot of advantages in comparison to fields:

• properties can be virtual

• properties hide implementation details (not all properties are just trivial variable accessors)

• properties can contain validation and logging code and raise change events

• interfaces cannot contains fields but properties