lifecycle

How can you tell when a windows 8 Metro app gets put in the background? The suspended state doesn't activate. I have a break point on. It only hits if I close the app. I am using a webcam and since no apps can run in the background I need to save my work when it's put in the background. The windows phone it was application deactivated. any help would be nice. Apps do not normally get suspended when in the debugger. However, you can force a suspend when debugging by: Enabling the Debug Location toolbar (red arrow in image below). Then press the Suspend button (blue arrow). The suspending event

For persistent storage of data is there any distinct advantage of using a SQLlite database over SharedPreferences or vice versa? Currently my application data is only a couple of kilobytes in size, though it could conceivably rise to ten times that size in the future. I can't find anywhere that states how much storage is available using SharedPreferences but would imagine this would be one limitation of using it? Is there any difference in speed between the two methods? I'm looking to weigh up the pros and cons of those two storage methods. Off the top of my head: SharedPreferences: Pro:

Can anybody tell me when Application_End is triggered in a lifecycle of an application? When all sessions are ended, will Application_End be triggered automatically? + Are there any other reasons why Application_End could be triggered? The application_end event primarily fires when the IIS pool is recycled or the application itself is unloaded. One other thing to note, that a change to a dependent file (say web.config) will cause the application to reload itself, which will in cause the application_end event to fire while it is closing itself off. To note, the only instance I found of the

Is there any lifecycle hook like window.onbeforeunload in Angular2? I already googled and searched on stackoverflow, but found nothing <div (window:beforeunload)="doSomething()"></div> or @Component({ selector: 'xxx', host: {'window:beforeunload':'doSomething'} .. )} or @Component({ selector: 'xxx', .. )} class MyComponent { @HostListener('window:beforeunload') doSomething() { } } This is how to listen to global events. I don't know if the special behavior of this event is supported where the return value is used as text for the conformation dialog. You can still use export class AppComponent

I know that a fragment's view hierarchy has to be inflated in onCreateView, but what other functionality can be in onCreateView vs. what should wait for onActivityCreated? My current implementation uses separate activities for everything, and a typical activity does most of its work in its onCreate method, including inflating the view, setting the content view, initializing the various widgets with data, setting up listeners, etc. So can this probably all be moved into onCreateView, or should some functions be put into an onActivityCreated method instead? If your view is static, then moving