据我所知,如果所有事件订阅者都使用该ThreadOption.PublisherThread选项(这也是默认选项),则事件同步执行并且订阅者可以修改EventArgs对象,因此您可以在发布者中拥有
myEventAggregator.GetEvent<MyEvent>().Publish(myParams)
if (myParams.MyProperty)
{
   // Do something
}
订阅者代码如下所示:
// Either of these is fine.
myEventAggregator.GetEvent<MyEvent>().Subscribe(MySubscribedMethod)
myEventAggregator.GetEvent<MyEvent>().Subscribe(MySubscribedMethod, ThreadOption.PublisherThread)
private void MySubscribedMethod(MyEventArgs e)
{
    // Modify event args
    e.MyProperty = true;
}
如果您知道应该始终同步调用事件,则可以为CompositePresentationEvent<T>覆盖该Subscribe方法的事件(而不是 )创建自己的基类,并且只允许订阅者使用该ThreadOption.PublisherThread选项。它看起来像这样:
public class SynchronousEvent<TPayload> : CompositePresentationEvent<TPayload>
{
    public override SubscriptionToken Subscribe(Action<TPayload> action, ThreadOption threadOption, bool keepSubscriberReferenceAlive, Predicate<TPayload> filter)
    {
        // Don't allow subscribers to use any option other than the PublisherThread option.
        if (threadOption != ThreadOption.PublisherThread)
        {
            throw new InvalidOperationException();
        }
        // Perform the subscription.
        return base.Subscribe(action, threadOption, keepSubscriberReferenceAlive, filter);
    }
}
然后不是派生MyEvent自CompositePresentationEvent,而是派生自SynchronousEvent,这将保证您将同步调用该事件并且您将获得修改后的内容EventArgs。