Issue Boostrapping Catalog from XAML in SL

Topics: Prism v4 - Silverlight 4
Oct 19, 2010 at 2:12 AM

To get started with Prism I took the UICompostion QS and added a new bottom region. Then I created a new module project based very closely after the included employee module project. I updated the catalog and set the module to inject into the new bottom region. When it ran the left and right regions loaded but the bottom region remained empty. When I debugged I got the message I have seen here on the boards about setting your project to copy its xap.  From what I read, using xaml config removes the need to add module references to the shell but after much frustration I added a reference to my new module. BAM, it worked. I went back and checked if I had missed the shell referencing the employee module - nope. Then I thought maybe the new entry in the catalog had a typo and was being ignored. Removing my new module from the xaml catalog caused the module to fail to load.

So it seems the catalog is getting populated with the new module info but when thee boostrapper tries to actually load the xap file the references fails. I'm guessing adding the reference is making up for an error in my xaml. Does anyone see an issue with the following entry?

Note: The module project, the namespace and the module class are all named ProjectInfoModule following the examples of modules like ModuleA used in other quick starts.


<prism:ModuleInfo Ref="ProjectInfoModule.xap"
                      ModuleType="ProjectInfoModule.ProjectInfoModule, ProjectInfoModule, Version=, Culture=neutral, PublicKeyToken=null"
                      InitializationMode="WhenAvailable" />  

Thank you,


Oct 19, 2010 at 5:50 PM

Hi Gary,

Nice to see that you started using Prism. Based on my understanding you added a new module in the UI Composition Quickstart, but it is not loaded. So I think that you can find interesting the following forum thread where user reported a similar scenario:

Please, take into account that in the aforementioned thread the user tried to load its module on demand, so you could avoid the step 3 over there.

Hope this helps.

Fernando Antivero


Oct 21, 2010 at 5:17 AM

Sorry for my delay in responding. Another project had my attention for the last day. The reason my module was not loading was that the web project's SL tab did not have a reference. here is the helpful line from the linked post for any readers.


Finally, and one of the most important parts, add a reference to your ModuleA.xap file in the Silverlight Application tab from the properties page of the RemoteModuleLoading.Silverlight.Web project.


Thank you for your patient help. Any plans for a VS integrated project template in the future? It seems much of the pain, at least for a newbie is undoing much of what VS does to help you create a non prism application. The learning curve would be a bit easier if we were not fighting against what VS thinks our intent is.