如何使用PRISM库实现区域间通信？按钮触发命令控制多View

Absolutely! PRISM is built specifically to handle cross-region, component-to-component communication scenarios like the one you described. The cleanest, most maintainable approach here uses PRISM's EventAggregator—a publish-subscribe pattern that keeps your regions loosely coupled (no direct references between components required). Let’s break down the implementation step by step.

Core Concept: EventAggregator #

EventAggregator lets components publish events without knowing who’s listening, and subscribe to events without knowing who’s publishing. This is perfect for your menu-to-RichTextBox workflow.

Step 1: Define a Shared Event Class #

First, create a reusable event class (usually in a shared project/assembly accessible to all your view models) to carry the text you want to send to the RichTextBoxes:

// Shared event class
public class UpdateRichTextEvent : PubSubEvent<string> { }

This event will pass a string payload—exactly what you need to update the RichTextBox content.

Step 2: Publish the Event from the Menu Region #

In your menu view model (the one tied to the button in the first region), inject IEventAggregator and use it to publish the event when the button is clicked:

public class MenuViewModel : BindableBase
{
    private readonly IEventAggregator _eventAggregator;

    // Bind this command to your menu button in XAML
    public ICommand SendTextToRegionsCommand { get; }

    public MenuViewModel(IEventAggregator eventAggregator)
    {
        _eventAggregator = eventAggregator;
        SendTextToRegionsCommand = new DelegateCommand(SendText);
    }

    private void SendText()
    {
        // Replace this with dynamic text (e.g., from an input field) if needed
        string textToSend = "Message from Menu Region!";
        // Publish the event to all subscribers
        _eventAggregator.GetEvent<UpdateRichTextEvent>().Publish(textToSend);
    }
}

In your menu view's XAML, bind the button to this command:

<Button Content="Send Text to Regions" Command="{Binding SendTextToRegionsCommand}" />

Step 3: Subscribe to the Event in RichTextBox Regions #

In the view models for your second and third regions (the ones with RichTextBoxes), subscribe to the event and update the bound text property when the event is received. Don’t forget to clean up the subscription to avoid memory leaks!

public class RichTextRegionViewModel : BindableBase, IDisposable
{
    private readonly IEventAggregator _eventAggregator;
    private SubscriptionToken _eventSubscription;
    private string _displayText = string.Empty;

    // Bind this property to your RichTextBox in XAML
    public string DisplayText
    {
        get => _displayText;
        set => SetProperty(ref _displayText, value);
    }

    public RichTextRegionViewModel(IEventAggregator eventAggregator)
    {
        _eventAggregator = eventAggregator;
        SubscribeToUpdateEvent();
    }

    private void SubscribeToUpdateEvent()
    {
        // Subscribe to the event and trigger the update method
        _eventSubscription = _eventAggregator.GetEvent<UpdateRichTextEvent>()
            .Subscribe(OnTextReceived);
    }

    private void OnTextReceived(string newText)
    {
        // Update the bound text property (PRISM's SetProperty handles INotifyPropertyChanged)
        DisplayText = newText;
    }

    public void Dispose()
    {
        // Unsubscribe to prevent memory leaks when the view model is discarded
        _eventAggregator.GetEvent<UpdateRichTextEvent>().Unsubscribe(_eventSubscription);
    }
}

Bind the RichTextBox to the DisplayText property in your view's XAML:

<RichTextBox>
    <FlowDocument>
        <Paragraph>
            <Run Text="{Binding DisplayText}" />
        </Paragraph>
    </FlowDocument>
</RichTextBox>

Advanced: Send Text to Specific Regions #

If you ever need to send different text to each RichTextBox region instead of the same text to both, modify the event to carry a target identifier:

// Updated event with targeted message
public class UpdateRichTextEvent : PubSubEvent<RichTextUpdateMessage> { }

public class RichTextUpdateMessage
{
    public string Text { get; set; }
    public string TargetRegionId { get; set; } // e.g., "Region2" or "Region3"
}

Publish with a target:

// Send different text to each region
_eventAggregator.GetEvent<UpdateRichTextEvent>().Publish(
    new RichTextUpdateMessage { Text = "For Region 2", TargetRegionId = "Region2" }
);
_eventAggregator.GetEvent<UpdateRichTextEvent>().Publish(
    new RichTextUpdateMessage { Text = "For Region 3", TargetRegionId = "Region3" }
);

Subscribe with a filter:

// Only listen for messages targeting this region
_eventSubscription = _eventAggregator.GetEvent<UpdateRichTextEvent>()
    .Subscribe(OnTextReceived, filter: msg => msg.TargetRegionId == "Region2");

This approach is fully aligned with PRISM's design principles and will work seamlessly for your three-region setup.

内容的提问来源于stack exchange，提问作者Mihail Ko