I have a situation in a current application I'm working on that requires featuring batch editing and I'm wondering if there are any design patterns that I should be considering.
The task at hand is given a collection of objects that represent files on disk the user can edit a property on one object and have the edit ripple to all objects in the collection.
The properties that are edited belong to child objects of the file object.
I'm using C# / .NET in this instance and, if possible, I'd like to avoid too much or any reflection, hence the question about design patterns.
Doing this with plain framework events and reflection is the most obvious path but I'd be really interested to know if there is an established pattern for dealing with this kind of scenario?