|
|
Rank: Member
Groups: Member
Joined: 9/27/2014
Posts: 15
|
hi Support,
I tried to update the version of "web browser" from 3.0.65.0 to 3.0.89.0 and I found the following problem:
With the previous vesion when I loaded a page I was surfing safely without running a "Handling New Window" as long as the site required the opening of a new page. So at some sites there was no need even to handle the event of the new window if the site did not require it.
With version 3.0.89.0 when I load any page, I get immediately the window eo.webbrowser inviting me to handle the event. The same page, if I open it with the previous version and with the same code does not give me message by, unless I open a link that requires a new window.
How can this happen?
something has changed in the new version?
thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi,
The only difference is in the new version it prompts you to handle NewWindow event when it is called. In the old version it is also called (which means the site did request to create a new window), but if you don't handle the event, then nothing will happen. If you just wish to ignore the request, you can handle the event but use an empty handler. That will silence the message.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 9/27/2014
Posts: 15
|
Thanks for the reply.
I realized that something was wrong with visual studio and I did more testing after restarting the system and control resumed normal operation in the management of new windows.
There is a method to upgrade a Visual Studio project that has references to the old dll of a web browser, without having to rewrite code or enter a new webview? When I replace the new webview appear many errors of references to the old contol.
thanks
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,196
|
Hi,
Sometimes Visual Studio is confused about multiple different versions. In that case you can:
1. Download and install the full download package from our download page;
2. Explicitly update your project reference to reference the DLL from the installation folder;
3. Rebuild your project;
That should clean up everything in your vs projects.
Thanks!
|
|