Question

Is there a way to continue to utilise auto-implemented properties while still raising a change event, such as INotifyPropertyChanged, when Set is called?

Instead of:

private string _value;
public string Value
{
  get 
  { 
    return this._value;
  }
  set
  {
    this._value = value;
    this.ValueChanged(this,EventArgs.Empty);
  }
}

Can I just do:

public string Value 
{ 
   get; 
   set 
   { 
     this.ValueChanged(this,EventArgs.Empty); 
   }
}

Although the setter looks wrong, is it possible to do this without filling my class with backing-store variables?

UPDATE: Looks like there is no standard solution to my lazy objective, I think that the best solution is to use CodeRush or Resharper to generate all my backing stores for me.

Answer 1

You can’t do this. The specification for automatically implemented properties is pretty clear:

Automatically implemented
(auto-implemented) properties automate
this pattern. More specifically,
non-abstract property declarations are
allowed to have semicolon accessor
bodies. Both accessors must be present
and both must have semicolon bodies,
but they can have different
accessibility modifiers. When a
property is specified like this, a
backing field will automatically be
generated for the property, and the
accessors will be implemented to read
from and write to that backing field.
The name of the backing field is
compiler generated and inaccessible to
the user.

In other words, they can only have “get;” and “set;“, with the possibility of access modifiers.