title: Why encapsulate this field?
body: <p>I've always been told to encapsulate ANY and ALL properties from a class...</p>
  
  <p>This is right:</p>
  
  <pre><code>private string propertyName;
  public string PropertyName
  {
      get { return propertyName; }
      set { propertyName = value; }
  }
  </code></pre>
  
  <p>And this is WRONG</p>
  
  <pre><code>Public string PropertyName;
  </code></pre>
  
  <p>I can't see where is the need of encapsulation... 
  the first code, for me, is just useless redundant code...
  there's no need for encapsulation of that field...</p>
  
  <p>So if anyone can justify the encapsulation ON THIS SCENARIO. 
  (I can understand on other scenarios).</p>