Application.Resuming Event

// Register
event_token Resuming(EventHandler<IInspectable> const& handler) const;

// Revoke with event_token
void Resuming(event_token const* cookie) const;

// Revoke with event_revoker
Application::Resuming_revoker Resuming(auto_revoke_t, EventHandler<IInspectable> const& handler) const;

public event System.EventHandler<object> Resuming;

function onResuming(eventArgs) { /* Your code */ }
application.addEventListener("resuming", onResuming);
application.removeEventListener("resuming", onResuming);
- or -
application.onresuming = onResuming;

Public Custom Event Resuming As EventHandler(Of Object) 

Event Type

Remarks

The system suspends your app whenever the user switches to another app or to the desktop, and resumes your app whenever the user switches back to it. However, the system can also terminate your app while it is suspended in order to free up resources. Therefore, you should handle the Suspending event to save your app state.

If your app is terminated, you can restore the app state in an OnLaunched method override. If your app resumes before it is terminated, the system restores the app state automatically. You should handle the Resuming event only if you need to refresh any displayed content that might have changed while the app is suspended, such as news feeds or the user's location.

Applications should avoid invoking code that puts a high load on the UI thread in response to Resuming. Doing so gives appearance to the user that the shell is being unresponsive, when in fact it is your application code that is the throttle point. Delegate operations to other threads if possible, or use a staged or virtualized approach for rebuilding views and UI whenever the application is resumed.

The Resuming event runs in the same apartment it was registered in.

Applies to

See also

• Suspending
• OnActivated(IActivatedEventArgs)
• Launching and resuming apps
• Processes threads and apartments