Geek asks and answers

Managing WebBrowser makes the whole application immune

I have a C # .NET 3.5 application with a built-in web browser. The browser is designed to point to remote sites (instead of local). Everything works fine, but when the page responds slowly, it causes my application to become unresponsive until the page is loaded.

I do not mind that the browser does not respond while it is doing its job, but the application is also too far from ideal.

Is there a good way to prevent this? It would be useful to run WebBrowser in a separate thread - is it a bit higher than my skill set right now, and I don't think the WebBrowser control really likes multithreading? But I can find out if necessary.

+5
source share
3 answers

See answer No. 2 on this question for a decision on how to run it in a separate thread: BackgroundWorker and WebBrowser Control

You can also read answer # 1, it will explain the behavior you see (blocking the UB-ad with WebBrowser).

+2
source

Be that as it may, I found that the main reason for this was my application running as an administrator. Exactly the same problem was discovered when using Internet Explorer - as such, I just rewrote bits that required administrator rights, so now I no longer see the original problem.

0
source

this only happened on win7, I use fiddler2 to track HTTP / HTTP traffic. I found a built-in web browser to visit this network: http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/disallowedcertstl.cab?50ff94e72ac1a75c;the do the following: http://support.microsoft .com / kb / 2730040 / en (method 2 or method 3). You can try it. You can also use .net framework4.0, then u does not have this problem.

0
source

More articles:


All Articles