This mini-session was delivered by Adina Trufinescu.
The agenda for this session was:
- Application Resume User Experience
- Application Lifecycle
- Phone Resource Management
- Key Developer Scenarios
Adina started by discussing the next version of Windows Phone, codenamed Mango, where there is much improvements in the area of returning to a previously active application.
To take advantage of this in your application you will need to recompile your application against the new developers tools.
Adina then explained the new application lifecycle in Mango, which includes a new “dormant” state.
This “dormant” state is another stage before tombstoning. In this state the application resources are almost entirly freed, except memory usage but the process is not closed.
So, returning from a dormant state doesn’t requires you to deserialize your data and reload state. Only if the application was actually tombstoned you must reload your state.
To know whether you came back from “dormant” state or “tombstoned” state you can check a new property named IsAppInstancePreserved.
Adina then presented exactly what kind of resources are cleaned on “dormant” state and who is in charge of getting them back once reactivated.
That’s it for now,