Seperate deployment of the modules?

May 23, 2008 at 11:47 PM
Edited May 24, 2008 at 1:15 AM
I stumbled upon Prism today and it's got my interest. I've been prototyping something very similar and I'm very glad to see the PnP team working on this. I pulled the latest bits drop down and I have a question about the dynamic loading of the modules. As I understand, each module would (or could) be developed and deployed independently. Am I correct in assuming that ClickOnce deployment will be supported, and if so, how does this relate to the modules? Edit*


I didn't go through the Modularity Quickstart.

When I see the different quickstarts, it looks to me that Prism is a guidance and NOT a framework. Is this correct?

There is an issue with modualrity on which I could use some guidance. If teams would be discretely developing modules, what would be the best approach for versioning? e.g. How would the modules be loaded if AD drives the ModuleLoaderService? My initial thought is DB driven module disovery and declarative security, use AD for roles, but as far as deployment, I'm a bit stumped.