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.
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
ICENIUM MONITOR AVAILABLE FOR DOWNLOAD.
Monitor and track applications built with Icenium at run-time. Reduce support by fixing run-time crashes as they occur, obtain user insights such as location and system configuration, find and remove application bottlenecks, and track which features are used most to help prioritize development.
Try Icenium with EQATEC Analytics today >>