Question

I am facing a problem that Application.DoEvents() can solve. The problem is that WebBrowser suppose to navigate to a url asnychronously but it does’t, and when I use Application.DoEvents() it solves that, I think this happens because the application handles some other events and doesn’t deliver the events of the navigation properly.

I read a little about this method and I understand that method will cause the application to handle all the currents events. Now I am a bit concern because I used a cannon to kill an ant, Can someone tell me if what I did is worthwhile?

Answer 1

The Application.Dovents() method makes all pending messages processed. That can cause:

1. Entering a code block twice before the current one finishes. (Let’s assume that you navigate your browser with a button click. User clicks the button and while your code is waiting browser to copmlete the user clicked again. In that case Application.Doevents() will cause processing that method before stepping next line.)

2. Interrupting critical codes. (Lets assume that you have a time consuming method and the user clicked close button. Your form will disappear but your code will continue to run. A real problem.

3. Many more UnExpected results.

However I feel sometimes using this method is necessary and an easy solution like webbrowser which is difficult to use in multithreading (especially when its visible). If you have to use this method you should be sure that user and other things (timers, buttons, events vs) don’t interrupt anything.
For a detailed discuss:Use of Application.DoEvents()