For those early in the adoption of Azure cloud computing with Silverlight as a front end, I ran into a couple of interesting issues on an Azure project. Here’s a quick rundown, along with the workaround/resolution, in case you run into the same.
Unable to load Silverlight xap
The first issue was the inability to load the Silverlight application’s xap file when hosting from the WebRole project. Hosting the Silverlight application within the WebRole is essential to prevent the additional work of cross domain service calls. Cross domain calls are possible, but unnecessary when you’re developing and hosting both the Silverlight application and the Azure services.
As it turns out, I didn’t have the correct mime type configured for loading Silverlight apps. A simple addition to IIS did the trick: map the .xap extension to application/x-silverlight-app.
Unable to debug Silverlight app
I finally got the Silverlight app loaded. But for some reason, I couldn’t debug when running the WebRole project as the start up project.
The solution was buried in the project properties for the WebRole project. On the Web settings tab, there are a set of checkboxes that specify which debuggers are enabled. Once I selected Silverlight, all was well and I could debug my app.
This information is explained in more detail in Jim Nakashima’s MSDN blog post:
http://blogs.msdn.com/jnak/archive/2009/01/16/debugging-silverlight-in-a-web-role-on-the-development-fabric.aspx
Subscribe to:
Post Comments (Atom)
0 comments:
Post a Comment