Hi,
We have a application developed in a VSTO which uses the eo webbrowser component.
I'm in the progress of setting up a new development machine. On my old machine the webbrowser works without problems but on
my new pc it locks the application if a the statement Browser.GetDOMWindow() != null is called.
The webpage is not loaded if i set the url by: Browser.Url = "<page>". If i set the url and inspect it immediately it is empty.
On the working environment i see my app starts 2 eowp processes and one of those contains another 2 eowp processes. (almost no cpu activity if the browser isn't used)
On my new pc only those first 2 processes are active and 1 of those is at 11% cpu and steadily increases memory.
A testapp made in a windows forms app works as expected. The new pc uses Office 365 and the old Office 2016.
But Office 365 and the application do work on other developers machines...
I get no error or exceptions but the browser just locks everything in de vsto (excell or outlook). If i kill the eowp process which uses 11% cpu the application starts responding again (but offcourse my browser isn't usable)
I hope you have some idea's which could help me?