Gracefully handle background tasks when tombstones apps

I am using async ctp and doing a task that runs in the background. It works fine, but an exception is thrown at startup, and the application is called a gravestone. The exception is that the database context is null.

The docs say:

When the application is broken over stones, the underlying database connection is closed. To return to its former state after the tomb, the application must fulfill repeated requests that it performed before being buried.

I tried using a cancel file, but this does not seem to work, as the connection is already closed. Any idea how to handle something like this?

0
source share
1

, , . - - .

( ) , , . - IsolationStorage .

0

All Articles