Loose Coupling of Modules

Topics: Prism v2 - WPF 3.5
Jan 19, 2010 at 8:50 PM

Hello! I'm new to Prism, just started to research it. The whole idea is seems to be clear for me, but on practice... And the first question that I'm faced after reviewing StockTrader example is:
How can we say that our app's dependencies is loose coupled if or main assembly (StockTraderRI) is roughly dependent on modules assemblies: StockTraderRI.Modules.Market, StockTraderRI.Modules.News and so on? I understand, it's because we add  modules in bootstrapper and we need to point type of module, so we need to reference assembly with this type. But doesn't it contradict with the loose coupling cardinally?

Jan 20, 2010 at 10:52 AM


Have you checked Prism quickstarts Quickstarts\Modularity, there are some example (Configuration..)

Jan 20, 2010 at 3:14 PM

Oh, thanks! These ones I've missed -)