Although I personally don’t know of any samples that load modules in different application domains (which is something Prism does not support out of the box), David
Hill does briefly deal with this subject in a comment from
this blog post, where he says: “Loading modules in separated AppDomains is not soemthing that we have planned on supporting out of the box in Prism. There are some complexities with this approach (in terms of interacting with the UI) which make
it something of a specialized scenario. You should be able to extend the module loader to do this on top of Prism though (e.g. using MAF).”