Functions and methods have a better status in the .Net world than they had in the Java world … They are now first class. This means that it is possible to assigne a function or an instance method to a variable, and pass it around as wished. Delegates are indeed very useful.
What about properties ? It’s a shame but they are not first class, they cannot be assigned to a variable, and if you ever used WinForms data bindings, I am sure you wrote the following quite a lot :
Creating a new AddBinding shareable function, the only presenter side property name hard coded in the gui could be “Value”, and the real property could explicitly be used to set up a binding. After using this kind of property in our work project, we discovered and expanded a lot more around it :
No need to test property event notifications every time, just test it once on the Property<T> class
Ultra simple property delegation
Reusable read only properties
Computed properties with dependencies, able to notify changes automaticaly
Properties able to validate their value, and notify precise errors to the UI