Prism with several modules and modules depends on

Question

Hi, I am in a scenario where I am going to have several modules, and let the modules depend on other modules.

They say that we are building a business system, while one part is billing, and we have customers in different industries.

Thus, one industry may want to use some tools and create an account in its path, while another industry may want to do it differently. Therefore, I think that we can make one module for each method of creating invoices, so when loading the application we can see in the configuration which module of the box invoice module should be loaded.

So, to my first question, is this a way to solve this problem or are there better solutions?

My next question is: where should I put them in a tree?

Should modules depending on the billing module be placed in the billing module or at the same level?

Answer 1

We decided to go with the modules, and I placed them under the dependent module in the tree. It's really cool.

Answer 2

First, I would work on creating a viewengine to load a view based on context criteria. Criteria can be tenant (domain name), device, view size, current topic (all of these interfaces depend on your view)

Perhaps using an approach such as a DataTemplateSelector, scattered across your views, requiring customization. You probably want to approach it like in asp.net mvc to allow views (so that you have the ability to override views) based on your search paths.

You will need to be able to download tenant styles for custom branding application resource.

I would step back, creating your small dependencies between the grains, until after the maintenance problem appears above. For business logic that needs to be set up, you can use the strategy template.

I see that it costs more time to figure it out and manage these long chains of dependencies. The implementation cost later (after it is required for a good business function) will take only a few hours using ModuleInfo, as described here: Silverlight PRISM Creating a custom module directory