Keep LOB Windows Store app from suspending


  • We have developed a very extensive LOB application for our company. It is running on dedicated windows 8.1 enterprise laptops and runs very well. However, when a user switches between our app and the desktop, sometimes even for a brief moment, our app suspends.

    I know how the application life cycle works, but is there a way we (having complete control over the OS and environment) keep our app from suspending?  A registry key possibly? 

    When we had a WPF version of the application, Windows  didn't decide to kill that for us when we opened up another app!  If there isn't a way to do this, there needs to be!


    Tuesday, June 17, 2014 4:29 PM


All replies

  • There is no way to keep the app from suspending. Why do you need this? What is the scenario?

    Depending on what you are doing you may want to move some tasks to a background task or to a desktop component.

    Tuesday, June 17, 2014 4:46 PM
  • We developed an application that is used by physicians in a hospital.  This is the only function they have on the devices they use.  The application should not get suspended because Windows thinks it should. 

    The laptops have plenty of memory, so our apps memory utilization should not be a concern.  We rely on custom built pub/sub messages from a server that tells our app when things happen in the hospital (so we don't have to poll every x seconds).  When our app goes to sleep, those pub/sub messages queue up on the server and eventually get deleted.  When our app wakes up, it needs to get the whole dump of pub/sub messages it missed and reload a lot of data.

    We do not cache patient related data on the client due to HIPAA concerns, even though the entire HDD is encrypted, so dumping a bunch of data to the disk is out of question.

    Like I said, this is not a typical WinRT app that MS envisioned. 

    Tuesday, June 17, 2014 6:19 PM
  • To keep things live and in memory you'll probably need to use a desktop component. You can have a background component talk to your server and expose data to the UI via a Brokered Windows Runtime Components for side-loaded Windows Store apps .

    Depending on the exact details you may be able to manage a background task to keep the communication with the server, but I'm not sure it could meet your no-persistence specs. See Supporting your app with background tasks

    Wednesday, June 18, 2014 4:40 AM