How to create a module which can have its own modules

Topics: Prism v2 - WPF 3.5
Aug 9, 2009 at 8:45 PM

I'm using CAG to build a modular application.  One possibility is that one of the modules will, itself, be modular.  In fact, making it extensible would be a key requirement.  Is there a standard approach to this sort of thing with CAG?

Aug 10, 2009 at 4:15 PM


Prism can help you on your scenario, but it depends on what a 'modular module' means in your case.
If you are thinking of a module that uses other modules and coordinates them, you can perfectly achieve it just by having this module depend on the required modules.
If you want some more flexible solution where the modules that compose this modular module are clearly separated for the rest of the application, you might think of an architecture where this module acts as the shell for the module it contains (with its own bootstrapped, container, module catalog, etc).

You could also check MEF which address the extensibility problem. 

Hope it helps! 

Matias Bonaventura

Aug 14, 2009 at 11:11 AM

Thanks for the response - I hadn't come across MEF so I'll look into that.  You've also given me food for thought re nestin Prism: do you know if there are any examples of this?