Dec 12, 2011 at 8:02 AM
Edited Dec 12, 2011 at 8:02 AM
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
instead of the default way:
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 http://xxxstorage.blob.core.windows.net
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?