I am new to wpf threading, now that we have backgroundworker and dispatcher classes, classic winforms threading issues are no longer a problem?
I am new to wpf threading, now that we have backgroundworker and dispatcher classes,
Share
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.
I am new to wpf threading, now that we have backgroundworker and dispatcher classes, classic winforms threading issues are no longer a problem?
I have plenty of hands on threading experience in a professional situation, including quite a bit with WPF, and I can tell you that it does not solve any of these problems.
It is nicer than winforms in that the Dispatcher gives you a more clear idea of what the threading model is, but it doesn’t go much further than that.
There isn’t really much more that it could do even if they wanted to. Threading is an inherently complicated and ugly thing, and you can’t just magically make it go away with a few GUI libraries