Intersoft Community - ClientUI - Building a Modular Application with UXShell Application Framework.

Building a Modular Application with UXShell Application Framework.

yudi — Tue, 22 May 2012 08:27:19 GMT

In your initial post, it is stated that as the Navigation framework with the Intersoft library did not work across project with pack Uri’s or through the MEFContentLoader.

Is it possible for you to create a running simple sample which shows this behaviour (completed with the information regarding current result and the expected result)? The sample will be very useful to determine the best solution of your specific scenario.

Building a Modular Application with UXShell Application Framework.

NeRane — Wed, 16 May 2012 09:14:11 GMT

This looks great. But when is the expected release date for 7? And can MEF be used with ClientUI as long as we dont export/import views?

Thank you,

Ryan

Building a Modular Application with UXShell Application Framework.

yudi — Wed, 16 May 2012 00:33:50 GMT

In his blog article that was published about a week ago, the Chief Software Architect of Intersoft Solutions, Mr. Jimmy, has introduced a built-in IoC container of the next release of ClientUI. The IoC container implemented in the ClientUI Framework supports both standalone usage and integration with UXShell. Using this approach enables developer to resolve the registered dependencies anywhere in the code, including the dynamic XAP applications that are loaded on demand at runtime.

For more detail information, please check the article in here. Let us hear your feedback regarding the preview of the implemented IoC container.

Building a Modular Application with UXShell Application Framework.

NeRane — Tue, 15 May 2012 17:39:22 GMT

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.