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.
The second answer by Martin in this link explains how the dispatcher can be used in a winforms app. This link explains the wpf side. So my question is – can we do this in a winforms app ? If not, why ? thank you
UPDATE: I have found this link also that shows the multiple app.run method mentioned by Henk below. However it does not use the wpf dispatcher. I wonder if there is a performance diff between using the wpf dispacther in winforms (my question) vs multiple app.runs
No matter what you do, you will be limited to using 1 thread (the UI thread) to update your windows (Winforms, WPF, native code). You can spawn as many worker threads as you want to do all the data gathering and prep work you need, however you’ll still have to use the UI thread to do the updates. Take a look at the Task or the BackgroundWorker classes to do this work.