3 ms·

The problem with this lifecycle assumption is that there is no way to opt out. I have a "metro" style SSH application, and windows regularly decides it should

The problem with this lifecycle assumption is that there is no way to opt out. I have a "metro" style SSH application, and windows regularly decides it should close it, which kills my active SSH sessions. I understand that they removed the ability to opt-out to force developers to change to a more appropriate model, but there are cases where a task cannot be suspended (because, for example, it's interacting with another computer). Having to re-log-in to my ssh session the 4th or 5th time in an hour is absolutely infuriating.

WorldMaker 10y ago
You can opt out by creating a background process. The thing that makes that part complicated is that there is a background process lifecycle to learn (including interactions between a UI process and background process). Also, Windows wants a bit more of an explicit knowledge than say classic Win32 about what the background process is for so it can best manage it. The support for background processes continues to improve. Windows 10, for instance, now supports a "single instance" background processing model where background processes can be seen as an invocation of the UI app (if already running) and vice versa (the UI app is presented as an invocation to the background process if that is already running) with hand-offs from one to the other, simplifying the programming of some of the interactions between background and UI for some apps.