Property vs public declaration variable in a class

Question

Possible Duplicate:
What is the difference between a field and a property in C#

what's the different between this:

class Name {
  public int x;
}

and this:

class Name {
  int cx;
  public int x {
    get { return cx; }
    set { cx = value; }
  }
}

is it the same thing or are there some differences? Thank you

You wouldn't believe it, but the documentation actually contains [an article](http://msdn.microsoft.com/en-us/library/9d65as2e(v=vs.80).aspx) on that precise subject. — Adam, Sep 12 '12 at 21:19
Plus: http://stackoverflow.com/questions/653536/difference-between-property-and-field-in-c-sharp-net-3-5 — Tim Schmelter, Sep 12 '12 at 21:25

score 4 · Accepted Answer · edited May 23 '17 at 10:34

They are different.

In the first x is a Field, in the latter x is a Property. While Properties are "accessed just like Fields" in code, this is just the beauty of C#; the different definitions actually result in different incompatible types¹.

Using auto-properties would be equivalent to the latter (but is much easier to write):

class Name {
    public int x { get; set; }
}

I like this answer by Brian Rasmussen, to a related/duplicated question:

Fields and properties look the same, but they are not [the same]. Properties are methods and as such there are certain things that are not supported for properties, and some things that may happen with properties but never in the case of fields.

The answer then goes on to list some key differences covering usage and observable semantics.

¹ Changing a Field to a Property (or vice-versa) is a type-breaking change and requires that early-bound (e.g. statically-typed) code is recompiled against the new type.

Property vs public declaration variable in a class

1 Answers1