Why do I need a private field that is exposed via public property?

Question

I\'m comming from Java world mainly. So, C# properties do look nice.

I know that with C# 3.0 or above I can use Automatic Properties. I like it even more :).

Answer 1

In the simple case nothing. However you are making it easier to maintain the interface to the class should the implementation of either of those two methods require additional code.

Take for instance if you need to add a changing event to the setter.

   public int Age {

     get { return age; }
     set { 
          if ( age != value) {
              age = value; 
              OnAgeChanged();
          }
      }     
   }

You can do this with a property and not break client code. A field does not have this advantage.