Silverlight - when to call monitor.Stop()

[Curt]

Can someone please provide some tips on how/when to call monitor.Stop() from a silverlight xap inside of a web browser?  Thanks!

[Soren]

Hi Curt,

This is a notorious difficult scenario, and unfortunately we haven't been able to nail down a rock solid solution for this (since we are building on top of the browser stack so you might be familiar with the issues regarding onbeforeunload etc. ). The issue with ensuring a call to Stop is that this ensures that the recorded data is either send to the server or persisted on the machine. Failing to call Stop, or calling stop at a point where both network and file access is gone holds the risk of losing data.

So a complete solution may combine the following methods:

• You can try listening for the Application.Exit event within Silverlight but from our experience both the network and possibly also the ability to write to isolated storage is already gone at this point.
• You can go to a more elaborate setup, trying to hook into the javascript unloading events that calls back into the silverlight application. We have better success with this though it is not without flaws, as it builds on top of the browsers own ability to detect unloads (which are somewhat flaky). You can get a good explanation here: http://stackoverflow.com/questions/3660560/how-to-detect-a-browser-refresh-from-silverlight-4

 
Hope this helps to at least outline the possible ways to attack the issue. As mentioned, we haven't been able to nail a rock solid solution but combining the methods above is as close as we've been able to get.

Let me know if you need further information

Regards,
Soren
Telerik

[Curt]

Thanks Soren. I noticed that the App Exit worked intermittently . I'll investigate the javascript technique.

[Soren]

Hi Curt,

Let me know about your findings

Regards,

Soren
Telerik