How often do you use System.Component.BackgroundWorker in your user interfaces? (even if)

I am sure that a responsive interface is what everyone is aiming for, and the recommended way to do this is to use BackgroundWorker to do this.

Is it easy to work with? Do you use it often? Or you have your own framework for long-term tasks and the reporting process.

I found that I use it quite a lot and even using my delegates where I need some kind of progress message.

+5
source share
6 answers

( - ), BackgroundWorker . , BackgroundWorker , , , , . , , , .

, Thread ( ThreadPool), BackgroundWorker, , Thread .

, Thread, plain void ThreadStart(), .

+3

BackgroundWorker . , , , Backgroundworker , . . .

+3

, \.
, . " ". Patric Smacchia .

+1

. "" , 2 (UI Worker), , Threading.

+1

@Gulzar : , .

, , , - .

async , , , BackgroundWorker RunWorkerCompleted RunWorkerCompletedEventArgs.Error.

, BackgroundWorker , , , , .

0

, , - . BackgroundWorker , , (join ..). , , RunWorkerCompleted . , , - , , . -.

, .

-1

All Articles