We have been using the Intersoft ClientUI component library for some time.  However we have been developing modular applications using Prism and MEF.  This has allowed us to follow a really noce code patter with dependency injection and runtime composition of certain screens. 

For example, our home screenw ith an outlook style navication would import all exported instances of INavigationItem in the application.  The MainPage.xaml did not know or care how many, what or anything about the loaded modules of our application and then use the imported objects to compose a unified menu representing all modules that had been loaded into the application.

We used this methodolgy extensively to build alot of the common pages of the application, such as a global user dashboard, etc.

This did cause us some heartburn as the Navigation framework with the Intersoft library did not work accross projects with pack Uri's or through our MEFContentLoader. 

Can this functionality be reproduced using the Intersoft UXShell and Application packages?  Any assistance or guidance here would be greatly appreciated.

You can reach me directly at ryan.ford@perryman-sw.com or post here. 

I would love to get the full power of the intersoft package again, but need to maintain the program model and dependency injection that we have acheived with MEF and Prism.