Prism MVVM development team needs your help

    In a recent twitter post, I noted that work on the Prism library was suspended after the release of version 4. In response to this, I received messages from Ade Miller (a former maiden leader in the patterns & practices team) and from Bob Brumfield (works in patterns & practices on Prism , Enterprise Library , and Windows Phone 7 guidance projects ).

    The meaning of the answers came down to the following: Prism is alive, there are no commits due to the fact that the team cannot work on the project all year round, and at the moment they are planning activities for the 2012 financial year. Bob also noted that it would be great for me to share with them my ideas about what I would like to see in this library in the future.

    From what I can point out, I would mention (everything relates to the version of the library in WP7):
    • Lack of built-in IoC container (lite version of Unity?);
    • Lack of the concept of modules, which is in Silverlight and WPF versions;
    • Lack of bootstrapper (convenient at least because App.xaml.cs is unloaded);
    • No simple examples of using Prism for WP7;
    • Support for binding is not implemented for ApplicationBarMenuItem (unlike ApplicationBarIconButton);
    • I really like the EventToCommand extension from the MVVMLight library. It would be great to have the same in Prism;
    • It would be great to add a few snippets so that, for example, INotifyPropertyChanged properties could be created in a few keystrokes;
    • Tombstoning support out of the box (not sure if this is a Prism task, perhaps they should prepare an example where it is nicely implemented at a basic level in the ViewModel);
    • Implementation of NavigationService in ViewModel. EventAggregator is not quite suitable for navigation, as It works quite slowly;
    • Probably something else that flew out of my head;

    I have suggested many ideas, but I believe that our community can generate much more ideas for implementation in the Prism library in the areas of WPF, Silverlight and WP7.

    If you have thoughts and wishes, leave them in the comments. I will collect, translate and transfer everything to the Prism team.

    Thanks in advance!

    Also popular now: