Hi there, I've spent a day going through the examples and using the prism 4 templates and wondering if I'm on the right track and have a question on the .xaps and loading them in.
I and my coworkers have just started using Prism 4 (with MEF & MVVM) and one thing that we need to do is beable to load new modules applied to the server without recompiling the web side project. Essentially if we could do what WPF does with a directory
search of XAP files for the project would be perfect; but from my understanding silverlight is sandboxed (even with evaluated permissions) and requires a service implementation.
Now I assume this is more MEF and the way todo this is building a custom ModuleCatalog that uses "Dynamic" (LazyLoading) Modules that get their ModuleInfo from a Service linked to a database (since silverlight is sandboxed and can't access a config
file). So my question is what of the .Xap files? I have to reference every assembly's .Xap in my .Web project every time I add a new project (Module) to my solution, do those need to be stored in a database and loaded in or can I just store it locally and
access them without a reference within the web? Or are these no longer needed to be referenced when we pass in the ModuleInfo to the ModuleCatalog; and if this is the case where does the .Xap files go?
Based on - http://mef.codeplex.com/wikipage?title=DeploymentCatalog&referringTitle=Recomposition
I'd want to use a DeploymentCatalog for Dynamic Modules
Based on - http://blogs.msdn.com/b/jimmytr/archive/2010/02/25/dynamically-loading-modulecatalog-in-composite-prism-silverlight-application.aspx
Snippet of code where a List of Modules is loaded in; its unity but same concept.
Thank you for any help you can give me,