You could declare a single event class to use for all of your aggregate events, and pass a string as it's payload, but I wouldn't really recommend that approach. Prism developers would find it very confusing.
You could declare a single event class to use for all of your aggregate events, and pass a string as it's payload, but I wouldn't really recommend that approach. Prism developers would find it very confusing. The Event Aggregator uses a different architecture than the old CAM.
I wasn't happy either about the need for an event object when I made the change. But I've since been sold on the approach--the event object is basically a one-liner that I generate using a ReSharper template. The reason I like it so much is that it gives me a place to put any logic I might need to go along with the event.
Writing a event class for every value to fire is stupid. – msfanboy Apr 1 at 19:21 Actually, it's rather intelligent. A well-designed application is like a Swiss watch, with each class acting as a gear in the overall assembly.
Each class does one thing well, and they all collaborate to perform the work required. Far less brittle, and more easily maintained, than the old monolithic style of programming. – David Veeneman Apr 2 at 15:31 For the swiss watch/knife your are right.
Each tool has its purpose. The question for me at the moment is what makes me faster developing. – msfanboy Apr 7 at 12:42 let me ask you one last thing about the CAB event system vs prism event aggregator: WITH CAB I always had to REGISTER for a certain string/dattype BEFORE an OnMethod was executed if the messenger did a send/notify.
Did this improve with prism event aggregator? Actually I ask myself how to send data to a Window I open because the ViewModel behind the Window is created AFTER the data is fired... so the OnMethod is never executed. – msfanboy Apr 7 at 14:11 I do my windows a little differently.My windows get everything from the VM; if they need to take action when they open, I have the window subscribe to its own DataContextChanged event.
The event fires when the VM is set, triggering an event handler in the window. The event handler does whatever is needed, getting its data from the VM. – David Veeneman Apr 9 at 23:47.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.