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.
how does it knows when to/not to marshal call to the UI thread in it’s progresschanged event handler?
I know SynchronizationContext.Current can do the trick, but this property is only set in the main UI thread, what if the backgroundworker is created on another background thread?
Can anybody kindly explain?
According to the Reflector, BackgroundWorker.RunWorkAsync which is called from the UI-thread uses AsyncOperationManager.CreateOperation.
This method accesses SynchronizationContext.Current (or creates a new if none exists).
So the SynchronizationContext is saved when starting the BGW.