Skip to main content

Return to Answer

Replace dead links with working archives, add HTTPS
Source Link
Ryan M ♦
Ryan M ♦
  • 20.6k
  • 35
  • 75
  • 85

A common pattern for this style of problem is MediatorMediator (a class that both view models reference and can be used to pass messages between the two).

The Mediator class has since been moved to the Cinch WPF/SL MVVM FrameworkCinch WPF/SL MVVM Framework, which appears to still be actively developed/supported.

The pattern I prefer is the Event AggregatorEvent Aggregator, an example can be found in the Prism framework. In this pattern different view models subscribe to events from the aggregator and others publish events.

Hope this helps

A common pattern for this style of problem is Mediator (a class that both view models reference and can be used to pass messages between the two).

The Mediator class has since been moved to the Cinch WPF/SL MVVM Framework, which appears to still be actively developed/supported.

The pattern I prefer is the Event Aggregator, an example can be found in the Prism framework. In this pattern different view models subscribe to events from the aggregator and others publish events.

Hope this helps

A common pattern for this style of problem is Mediator (a class that both view models reference and can be used to pass messages between the two).

The Mediator class has since been moved to the Cinch WPF/SL MVVM Framework, which appears to still be actively developed/supported.

The pattern I prefer is the Event Aggregator, an example can be found in the Prism framework. In this pattern different view models subscribe to events from the aggregator and others publish events.

Hope this helps

Updated info on the Mediator class; original link remains as a 'sample' of what a basic Mediator would do.
Source Link
edit approved Jul 11, 2014 at 13:30
Forest Kunecke
edit approved Jul 11, 2014 at 13:30
Forest Kunecke
  • 2.2k
  • 15
  • 33

A common pattern for this style of problem is Mediator (a class that both view models reference and can be used to pass messages between the two).

The Mediator class has since been moved to the Cinch WPF/SL MVVM Framework, which appears to still be actively developed/supported.

The pattern I prefer is the Event Aggregator, an example can be found in the Prism framework. In this pattern different view models subscribe to events from the aggregator and others publish events.

Hope this helps

A common pattern for this style of problem is Mediator (a class that both view models reference and can be used to pass messages between the two).

The pattern I prefer is the Event Aggregator, an example can be found in the Prism framework. In this pattern different view models subscribe to events from the aggregator and others publish events.

Hope this helps

A common pattern for this style of problem is Mediator (a class that both view models reference and can be used to pass messages between the two).

The Mediator class has since been moved to the Cinch WPF/SL MVVM Framework, which appears to still be actively developed/supported.

The pattern I prefer is the Event Aggregator, an example can be found in the Prism framework. In this pattern different view models subscribe to events from the aggregator and others publish events.

Hope this helps

Source Link
Nigel Sampson
Nigel Sampson
  • 10.6k
  • 1
  • 30
  • 32

A common pattern for this style of problem is Mediator (a class that both view models reference and can be used to pass messages between the two).

The pattern I prefer is the Event Aggregator, an example can be found in the Prism framework. In this pattern different view models subscribe to events from the aggregator and others publish events.

Hope this helps