title: Use of properties vs backing-field inside owner class
body: <p>I love auto-implemented properties in C# but lately there's been this elephant standing in my cubicle and I don't know what to do with him.</p>
  
  <p>If I use auto-implemented properties (hereafter "aip") then I no longer have a private backing field to use internally. This is fine because the aip has no side-effects. But what if later on I need to add some extra processing in the get or set? </p>
  
  <p>Now I need to create a backing-field so I can expand my getters and setters. This is fine for external code using the class, because they won't notice the difference. But now all of the internal references to the aip are going to invoke these side-effects when they access the property. Now all internal access to the once aip must be refactored to use the backing-field.</p>
  
  <p>So my question is, what do most of you do? Do you use auto-implemented properties or do you prefer to always use a backing-field? What do you think about properties with side-effects?</p>