April 10 Drop

Apr 15, 2013 at 3:00 PM
Nice, I like how you've moved to using the Prism namespace. Much easier to get management on board where you're using a known name for a technology.

Also like how the eventaggregator is changing to support similar signatures as the pre-existing EventAggregator.

These all help with take up (and less of a learning curve for people already invested in Prism).
Apr 19, 2013 at 9:53 PM

Thanks for the feedback and it is good to hear that it is helpful to use the Prism namespace.

Next week I will publish a blog post on the name of the library and its associated namespaces.

As we evaluated what to name the library, we wanted devs to understand that the library is different from Prism for WPF and Silverlight but some of the scenarios are the same - loose coupled pub/sub, separation of concerns with MVVM, and so on. We decided calling the new library Prism for Windows Runtime would accomplish this goal.