Good to see your perceptions on the current hot subject. I agree with all of your points but that doesn’t mean that we shoudn’t support it. There is no rule / no bill is going to make the entire system corruptless. Majority of them are supporting even though they are not aware of this bill detail to have something instead of nothing.

If we think in this direction, I don’t think there is nothing harm to support this movemnt..

.N. Rao

Practical advice for anyone considering implementing IEditableObject for your custom Business Object class, create a struct inside your class, and inside of that store all of your actual data. Then, keep 2 instances of your struct inside the class, one as your backup, and one within which to perform your operations. This is also a good opportunity to run a validation check, should your object support it.

Outside of the struct, you would need public Get/Set accessors for each property, which would be a useful thing should you also wish to implement INotifyPropertyChanged.

var collection = System.Windows.Interactivity.Interaction.GetBehaviors(this);
collection.Add(new BorderlessWindowBehavior());

Hope this helps