Is there any better way to avoid this Exception?

Question

Here's what it does:

So when it takes fair amount of time in between BusyWindow.Activate and BusyWindow.Terminate, I don't get that exception, printing PDF or actual page for example, BUT when it takes less time I get that! How to avoid that without sleeping for some time?

EDIT
----
The Azure blocking issue, I mentioned earlier, is with dot Sleep after Thread. Updated the project in GitHub and put a sleep immediately after thread.Start() in Activate function of BusyWindow.cs, remove that to get into the issue.

Answer 1

The two operations affect each other, probably because window is a global variable. Please add window = null; before the var thread = new Thread... in Activate. I tested with this added and it works well.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.