The only reason I chose to use a BackgroundWorker
for the application I am currently developing is to move the lengthy time-consuming browsing via a WebBrowser
away from the UI thread.
But isn't WebBrowser.Navigate()
accessing the UI?
In other words, I went through all this effort, only to land in the same spot (or worse! because I have no idea what side-effects could a non-UI thread have when accessing UI controls).
I am pretty sure I am not the first one wanting to implement something like this, so my question is: What is an acceptable way to solve this problem? i.e. To WebBrowser.Navigate()
from BackgroundWorker
?