PRISM - When is the module catalogue's modules registered with the container?

[Phillip Donegan]

Hi All, As the title says really, when in PRISM are each of the modules in the module catalog registered with the container (in my case Castle). And can I override it? Basically the problem I have is that when doing this for example:

        this.ModuleCatalog.AddModule(AvailableApplicationModules.SampleModule);

At some point that module is then registered with the container. Now in castle atleast when doing this if no Name is specified (which it isn't) then the default AssemblyQualifiedName of the implementation is used. This includes the version number and is causing problems on the build server when it will always be dynamic. So my plan is the set the .Name property when the module is registered with the container so that I can retrieve the module by using:

this.windsorContainer.Resolve(string Key)

But I can't find the part were the modules are registered with the container. I'm presuming that PRISM itself takes care of this so I guess I need to override something.

[Abhinav S]

Prism is open source. So you can probably look at the source code itself to get a better idea. You can use the IModuleCatalog interface if you want to implement something on your own.

Too much of heaven can bring you underground Heaven can always turn around Too much of heaven, our life is all hell bound Heaven, the kill that makes no sound