In two previous columns, I've showed how to build a composable application in WPF with Prism and Unity. A composable application consists of the main Shell (a WPF application with a XAML Window) and a set of Modules, each containing one part of the application's functionality.

My first column in this series on creating self-assembling, composable WPF applications showed how to create the Shell (main application) and a Module that defined part of the UI. The second column showed how to add in a Module that provided business functionality. But just because the application "knows" about a module that provides the functionality, it doesn't mean the application will use it. The next step is to decide where you're going to apply that business functionality (or "service," in Prism-speak).

Read More from: Original Source

I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

C#,.NET,Intermediate,Advanced,VS2010,WPF,XAML,Services