Has anyone else run into this problem? I'm growing fond of the EventAggretator pattern to communicate between loosely coupled components. However, there's no persistence to the event and it's getting to be a problem. I have an application where a URI is used to select the object being viewed. Once everything is loaded, the volatile event works just fine, but on initialization you don't know if the event has fired or not. Let's say that Region 1 fires the UriChanged event. Region 2 has no idea when it loads if the event has fired or not so it can end up uninitialized. I've solved the problem by providing a shared object through the CompositionContainer ("SharedUri") to go with the UriChanged event, but it would be much easier if I could just query the last value of the UriChanged event.
↧