Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it possible “kill” the thread of a BackgroundWorker?
In my DoWork event, I can’t check the cancellation flag, because I have a blocking
call to an external COM interface or a query to a database. CancelAsync doesn’t cancel the call to COM.
How can I do it, please ? Any suggestions will be very appreciated.
Thanks in advance.
I’m not aware of a safe way to abort a thread.
A background worker can check if it should cancel and cancel itself, but if it’s off querying a database there’s not much you can do until it returns.
You can do work on a ThreadPool thread and just abandon the thread and start another if it’s not needed anymore (making sure that when it comes back from a db query it checks if it should cancel before doing anything nasty). Of course you’d need to balance the performance and manage thread synchronisation. If you go down that path, you could take a look at the Interlocked static class for efficient critical section locking.