The only reason I decided to use BackgroundWorker for the application I'm currently developing is to move the long-running multi-user view through the WebBrowser away from the user interface stream.
But doesn't WebBrowser.Navigate() access the user interface?
In other words, I went through all these efforts just to land in the same place (or, even worse, because I have no idea what side effects a non-UI stream may have when accessing user interface controls) .
I am sure that I am not the first who wants to implement something like this, so my question is: what is an acceptable way to solve this problem? those. to WebBrowser.Navigate() from BackgroundWorker ?
source share