.NET Rx and Composite Framework (Prism) Event aggregator

Answered .NET Rx and Composite Framework (Prism) Event aggregator

  • Wednesday, November 18, 2009 12:53 AM
     
     
    Hi there,

    Anybody knows how .NET Rx will affect the Event aggregator in WPF Prism composite app framework?

    Tony
    TW

All Replies

  • Wednesday, November 18, 2009 3:39 PM
     
     Answered
    Hi Tony,

    Looks like we should be able to create an adapter between EventBase and IObservable. I'll file a bug to look into this.

    Thanks for the feedback!

    Jeffrey
  • Wednesday, November 18, 2009 10:27 PM
     
     

    Hi,

    Someone is already thinking about it, use nRoute instead of Prism :)
    http://www.orktane.com/Blog/post/2009/09/29/Introducing-nRouteToolkit-for-Silverlight-(Part-I).aspx

    mn

  • Thursday, December 10, 2009 4:28 PM
     
     
    Any update on this?

    I am trying to push Rx into the greenfiled core framework we are currently building.  It uses Prism and currently relies on the event aggregator to signal events between the various UI modules. What I am struggling to understand is how Rx would fit into this model and why would I choose it over the event aggregator?

    The nRouteToolkit creates ObservableChannels that leverage IObserver and IObservable to substitute the event aggregator. Is this really worth the effort?


    Pure Complexity
  • Thursday, June 24, 2010 1:31 PM
     
     Proposed Answer

    Nick: I wrote an adaptor for Rx to Prism's IEventAggregator that may help.

    http://richarddingwall.name/2010/03/30/reactive-extensions-and-prism-linq-to-your-event-aggregator/