Migrating Prism v2 Silverlight applications from static to dynamic module loading
The P&P Sustained Engineering Team has published an article in the Composite WPF & Silverlight Knowledge Base that explains how to modify the Prism v2 Silverlight Reference Implementation so it uses Dynamic Module Loading. By doing this, each module generates its own XAP file and the ModulesCatalog.xaml file in the Shell project defines how modules should be loaded:
As I mentioned, the article targets the migration of the Silverlight Reference Implementation included in the Prism V2 - Drop 10, but you could use it as a guidance to migrate any Prism v2 Silverlight application from static to dynamic (remote) module loading. The main steps are:
- Update Silverlight class library projects to Silverlight application projects to generate XAP files
- Set up remote module loading by adding a ModulesCatalog.xaml file and modify the Bootstrapper class
- Create a Web Application Project to host the application
The team also published the following:
- The PDF version of the article
- The updated source code of the Silverligh RI
| Disclaimer: The code is provided “AS IS” with no warranties, and confers no rights. |