Dynamic loading of model assemblies (Prism)

We are building a Prism-based application that dynamically loads prism modules based upon UI events (such as Silverlight navigation). Some of these modules include IdeaBlade functionality, so we were intending to have them register their data models by adding them to the IdeaBladeConfig.ProbeAssemblyNames collection when the module is loaded and initialized. Unfortunately, it appears that there is some point at which IdeaBlade performs a definitive scan of that list of ProbeAssemblyNames. If we have the main Prism host download and register the model assembly on application startup all works properly, but if we download and register the model assembly on-demand, it fails with serialization exceptions stating it cannot locate the type information such as the below:

Is there a way to force a refresh of the known types after updating the ProbeAssemblyNames collection rather than requiring us to load & register all model assemblies at startup? The list could get quite long, which can make the application take longer to start.

 

-Andy Hopper

 

The only thing I can think of is to start communications as late as possible.   On the client this means creating a disconnected EntityManager and calling ConnectAsync only after your model assemblies are loaded and registered.  This might carry through to the server too, since it's the EntityServer which needs known type information, and it's the EntityServer service which is started on the first client Connect.