从抽象类继承静态事件的 INotifyPropertyChanged

Question

I'm trying to implement a number of Abstraction Layers for various pieces of hardware, and I've found I've implemented the same function, NofityStaticPropertyChanged (from here ) about 5 times.

    /// <summary>
    /// A slightly different implementation of Static Property Changed, from here:
    /// https://stackoverflow.com/a/42111290/2444435
    /// </summary>
    public static event PropertyChangedEventHandler StaticPropertyChanged;

    protected static void NotifyStaticPropertyChanged(string propertyName)
    {
        StaticPropertyChanged?.Invoke(null, new PropertyChangedEventArgs(propertyName));
    }

I'd like to have all of these classes inherit from an abstract class AbstractionBase to avoid reusing code.

I've read elsewhere as to how to inherit this sort of function for non-static members, but I'm never actually instantiating these abstraction layers/factories.

I'm not sure this is actually possible, since static properties cannot be inherited. I feel like it ought to be though, since it's basically a function, not a property? My current attempt is thus:

public abstract class AbstractionBase : INotifyPropertyChanged
{
    //THIS IS NOT WORKING!
    #region INofity Declarations
    /// <summary>
    /// A slightly different implementation of Static Property Changed, from here:
    /// https://stackoverflow.com/a/42111290/2444435
    /// </summary>
    public static event PropertyChangedEventHandler StaticPropertyChanged;

    protected static void NotifyStaticPropertyChanged(string propertyName)
    {
        StaticPropertyChanged?.Invoke(null, new PropertyChangedEventArgs(propertyName));
    }

    #endregion
} 

Thanks! I have a feeling I might not be able to get away with this de-duplication attempt, but if it is possible, then that'd be nifty!

Answer 1

WPF 4.5 supports binding to static properties, all you have to do is create a static event handler of the same name with the text "Changed" appended, and you invoke that instead of your StaticPropertyChanged:

public class MyStaticClass
{
    public static event EventHandler MyStaticPropertyChanged;

    private static string _MyStaticProperty = "Hello World!";
    public static string MyStaticProperty
    {
        get { return _MyStaticProperty; }
        set
        {
            if (_MyStaticProperty != value)
            {
                _MyStaticProperty = value;
                MyStaticPropertyChanged?.Invoke(null, EventArgs.Empty);
            }
        }
    }
}

Which you would bind to like this:

<TextBlock Text="{Binding Path=(vm:MyStaticClass.MyStaticProperty), Mode=OneWay, UpdateSourceTrigger=PropertyChanged}" />

Honestly though, this looks like more of an architectural issue to me. If you're using a dependency injection framework...and you should be....then there's absolutely no need to use static properties for anything, just place them in their own class and set up your DI to make it a singleton.