PRISM on the Azure Cloud?

Topics: Prism v4 - Silverlight 4
Dec 12, 2011 at 8:02 AM
Edited Dec 12, 2011 at 8:02 AM

Hey guys,


 I have deployed a Silverlight/Prism project on Azure Cloud.  Everything works fine as long as the XAPs are located on the actual Virtual Machine (VM).

But generally its best to store to the XAPs on the storage and point from default.aspx directly to it

1) <param name="source" value=""/>

instead of the default way:

2) <param name="source" value="ClientBin/SalesContactManagement.Shell.xap"/>

While this works and the app is loaded up, there seem to be no connection to the database at all.
Now with the help of Microsoft Support we were able to trace it down to the following:




The trace above is wrong as the service is not located on

But when we use method 2) that is accessing the XAPs locally, we get the correct trace:




I wonder if this is something related due the nature of PRISM module discovery and if somebody came across these issues before?

Many Thanks,


Dec 12, 2011 at 8:53 PM

Hi Houman,

Take into account that Prism is a set of guidances and practices designed to help developing modular based applications in Silverlight or WPF, wich includes the Prism Library, that runs on the client side. On the other hand Azure provides a server environment which allows you to distribute Silverlight applications.

Based on my understanding, once the application is distributed to the client, Windows Azure should not affect the application. So using Prism on Azure should be the same as in a normal Silverlight application. Therefore I believe you might find better support on Windows Azure's forum.


Agustin Adami