Vital Stages in the Lifecycle of a Windows Store App
There are four critical states in the lifecycle of a Windows Store app. They are as per the following:
- Not Running
The Not Running state is very clear. In this express, an application is not running by any stretch of the imagination. An application may go into this state because of different reasons. For instance, a client may have quite recently introduced the application, however, has never propelled it. Another plausibility is that a client may have finished the application utilizing the Undertaking Chief or might have quite recently restarted the PC.
When you dispatch an app it changes its state from Not Rushing to Running. Such an app is the one that the client is connecting with at a given purpose of time and the OS has assigned required assets for it.
An app in the Running state can enter the Suspended state for a few reasons. Say a client propelled application App1, utilized it for quite a while and after that changed to some other application, App2. For this situation, the OS suspends App1 subsequent to sitting tight for five seconds. This is done to moderate framework assets. Since the client is utilizing App2 now, App1 is suspended keeping in mind the end goal to give assets to App2. The suspended application is still held in the memory, however, none of its code runs. In the event that the client changes to App1 again it goes into Running state and obviously, App2 is presently suspended.
The four conditions of a Windows Store app
Keeping up App State