.NET Core 3 WPF MVVM框架 Prism系列之事件聚合器

本文将介绍如何在.NET Core3环境下使用MVVM框架Prism的使用事件聚合器实现模块间的通讯html

一.事件聚合器

 在上一篇 .NET Core 3 WPF MVVM框架 Prism系列之模块化 咱们留下了一些问题，就是如何处理同模块不一样窗体之间的通讯和不一样模块之间不一样窗体的通讯，Prism提供了一种事件机制，能够在应用程序中低耦合的模块之间进行通讯，该机制基于事件聚合器服务，容许发布者和订阅者之间经过事件进行通信，且彼此之间没有之间引用，这就实现了模块之间低耦合的通讯方式，下面引用官方的一个事件聚合器模型图：
二.建立和发布事件

1.建立事件

 首先咱们来处理同模块不一样窗体之间的通信，咱们在PrismMetroSample.Infrastructure新建一个文件夹Events,而后新建一个类PatientSentEvent，代码以下：
PatientSentEvent.cs:github

public class PatientSentEvent: PubSubEvent<Patient>
{
}

2.订阅事件

 而后咱们在病人详细窗体的PatientDetailViewModel类订阅该事件，代码以下：
PatientDetailViewModel.cs:c#

public class PatientDetailViewModel : BindableBase
 {
    IEventAggregator _ea;
    IMedicineSerivce _medicineSerivce;

    private Patient _currentPatient;
     //当前病人
    public Patient CurrentPatient
    {
        get { return _currentPatient; }
        set { SetProperty(ref _currentPatient, value); }
    }

    private ObservableCollection<Medicine> _lstMedicines;
     //当前病人的药物列表
    public ObservableCollection<Medicine> lstMedicines
    {
        get { return _lstMedicines; }
        set { SetProperty(ref _lstMedicines, value); }
    }
  
     //构造函数
    public PatientDetailViewModel(IEventAggregator ea, IMedicineSerivce medicineSerivce)
    {
        _medicineSerivce = medicineSerivce;
        _ea = ea;
        _ea.GetEvent<PatientSentEvent>().Subscribe(PatientMessageReceived);//订阅事件
    }
     
     //处理接受消息函数
    private void PatientMessageReceived(Patient patient)
    {
        this.CurrentPatient = patient;
        this.lstMedicines = new ObservableCollection<Medicine>(_medicineSerivce.GetRecipesByPatientId(this.CurrentPatient.Id).FirstOrDefault().LstMedicines);
        }
    }

3.发布消息

 而后咱们在病人列表窗体的PatientListViewModel中发布消息，代码以下：
PatientListViewModel.cs:app

public class PatientListViewModel : BindableBase
{

    private IApplicationCommands _applicationCommands;
    public IApplicationCommands ApplicationCommands
    {
        get { return _applicationCommands; }
        set { SetProperty(ref _applicationCommands, value); }
    }

    private List<Patient> _allPatients;
    public List<Patient> AllPatients
    {
        get { return _allPatients; }
        set { SetProperty(ref _allPatients, value); }
    }

    private DelegateCommand<Patient> _mouseDoubleClickCommand;
    public DelegateCommand<Patient> MouseDoubleClickCommand =>
        _mouseDoubleClickCommand ?? (_mouseDoubleClickCommand = new DelegateCommand<Patient>(ExecuteMouseDoubleClickCommand));

    IEventAggregator _ea;

    IPatientService _patientService;

        /// <summary>
        /// 构造函数
        /// </summary>
    public PatientListViewModel(IPatientService patientService, IEventAggregator ea, IApplicationCommands applicationCommands)
    {
         _ea = ea;
         this.ApplicationCommands = applicationCommands;
         _patientService = patientService;
         this.AllPatients = _patientService.GetAllPatients();         
    }

    /// <summary>
    /// DataGrid 双击按钮命令方法
    /// </summary>
    void ExecuteMouseDoubleClickCommand(Patient patient)
    {
        //打开窗体
        this.ApplicationCommands.ShowCommand.Execute(FlyoutNames.PatientDetailFlyout);
        //发布消息
        _ea.GetEvent<PatientSentEvent>().Publish(patient);
    }

}

效果以下：
框架

4.实现多订阅多发布

 同理，咱们实现搜索后的Medicine添加到当前病人列表中也是跟上面步骤同样,在Events文件夹建立事件类MedicineSentEvent:异步

MedicineSentEvent.cs:async

public class MedicineSentEvent: PubSubEvent<Medicine>
 {

 }

 在病人详细窗体的PatientDetailViewModel类订阅该事件：
PatientDetailViewModel.cs:模块化

public PatientDetailViewModel(IEventAggregator ea, IMedicineSerivce medicineSerivce)
 {
      _medicineSerivce = medicineSerivce;
      _ea = ea;
      _ea.GetEvent<PatientSentEvent>().Subscribe(PatientMessageReceived);
      _ea.GetEvent<MedicineSentEvent>().Subscribe(MedicineMessageReceived);
 }

 /// <summary>
 // 接受事件消息函数
 /// </summary>
 private void MedicineMessageReceived(Medicine  medicine)
 {
      this.lstMedicines?.Add(medicine);
 }

 在药物列表窗体的MedicineMainContentViewModel也订阅该事件：
MedicineMainContentViewModel.cs：函数

public class MedicineMainContentViewModel : BindableBase
{
   IMedicineSerivce _medicineSerivce;
   IEventAggregator _ea;

   private ObservableCollection<Medicine> _allMedicines;
   public ObservableCollection<Medicine> AllMedicines
   {
        get { return _allMedicines; }
        set { SetProperty(ref _allMedicines, value); }
   }
   public MedicineMainContentViewModel(IMedicineSerivce medicineSerivce,IEventAggregator ea)
   {
        _medicineSerivce = medicineSerivce;
        _ea = ea;
        this.AllMedicines = new ObservableCollection<Medicine>(_medicineSerivce.GetAllMedicines());
        _ea.GetEvent<MedicineSentEvent>().Subscribe(MedicineMessageReceived);//订阅事件
   }

   /// <summary>
   /// 事件消息接受函数
   /// </summary>
   private void MedicineMessageReceived(Medicine medicine)
   {
        this.AllMedicines?.Add(medicine);
   }
}

在搜索Medicine窗体的SearchMedicineViewModel类发布事件消息：
SearchMedicineViewModel.cs:

IEventAggregator _ea;

 private DelegateCommand<Medicine> _addMedicineCommand;
 public DelegateCommand<Medicine> AddMedicineCommand =>
     _addMedicineCommand ?? (_addMedicineCommand = new DelegateCommand<Medicine>(ExecuteAddMedicineCommand));

public SearchMedicineViewModel(IMedicineSerivce medicineSerivce, IEventAggregator ea)
{
     _ea = ea;
     _medicineSerivce = medicineSerivce;
     this.CurrentMedicines = this.AllMedicines = _medicineSerivce.GetAllMedicines();
 }

 void ExecuteAddMedicineCommand(Medicine currentMedicine)
 {
     _ea.GetEvent<MedicineSentEvent>().Publish(currentMedicine);//发布消息
 }

效果以下：

而后咱们看看如今Demo项目的事件模型和程序集引用状况，以下图：

 咱们发现PatientModule和MedicineModule两个模块之间作到了通信，但却不相互引用，依靠引用PrismMetroSample.Infrastructure程序集来实现间接依赖关系，实现了不一样模块之间通信且低耦合的状况

三.取消订阅事件

 Prism还提供了取消订阅的功能，咱们在病人详细窗体提供该功能，PatientDetailViewModel加上这几句：
PatientDetailViewModel.cs:

private DelegateCommand _cancleSubscribeCommand;
 public DelegateCommand CancleSubscribeCommand =>
       _cancleSubscribeCommand ?? (_cancleSubscribeCommand = new DelegateCommand(ExecuteCancleSubscribeCommand));

  void ExecuteCancleSubscribeCommand()
  {
      _ea.GetEvent<MedicineSentEvent>().Unsubscribe(MedicineMessageReceived);
  }

效果以下：

四.几种订阅方式设置

 咱们在Demo已经经过消息聚合器的事件机制，实现订阅者和发布者之间的通信，咱们再来看看，Prim都有哪些订阅方式，咱们能够经过PubSubEvent类上面的Subscribe函数的其中最多参数的重载方法来讲明：

Subscribe.cs:

public virtual SubscriptionToken Subscribe(Action<TPayload> action, ThreadOption threadOption, bool keepSubscriberReferenceAlive, Predicate<TPayload> filter);

1.action参数

其中action参数则是咱们接受消息的函数

2.threadOption参数

ThreadOption类型参数threadOption是个枚举类型参数，代码以下：
ThreadOption.cs

public enum ThreadOption
{
        /// <summary>
        /// The call is done on the same thread on which the <see    cref="PubSubEvent{TPayload}"/> was published.
        /// </summary>
        PublisherThread,

        /// <summary>
        /// The call is done on the UI thread.
        /// </summary>
        UIThread,

        /// <summary>
        /// The call is done asynchronously on a background thread.
        /// </summary>
        BackgroundThread
}

三种枚举值的做用：

• PublisherThread：默认设置，使用此设置能接受发布者传递的消息
• UIThread：能够在UI线程上接受事件
• BackgroundThread：能够在线程池在异步接受事件

3.keepSubscriberReferenceAlive参数

默认keepSubscriberReferenceAlive为false，在Prism官方是这么说的，该参数指示订阅使用弱引用仍是强引用，false为弱引用，true为强引用：

• 设置为true，可以提高短期发布多个事件的性能，可是要手动取消订阅事件，由于事件实例对保留对订阅者实例的强引用，不然就算窗体关闭，也不会进行GC回收.
• 设置为false，事件维护对订阅者实例的弱引用，当窗体关闭时，会自动取消订阅事件，也就是不用手动取消订阅事件

4.filter参数

 filter是一个Predicate 的泛型委托参数，返回值为布尔值，可用来订阅过滤，以咱们demo为例子，更改PatientDetailViewModel订阅，代码以下：
PatientDetailViewModel.cs：

_ea.GetEvent<MedicineSentEvent>().Subscribe(MedicineMessageReceived,
ThreadOption.PublisherThread,false,medicine=>medicine.Name=="当归"|| medicine.Name== "琼浆玉露");

效果以下：

五.源码

 最后，附上整个demo的源代码：PrismDemo源码