Internet explorer 8 does not support the textcontent property

INTERNET EXPLORER 8 DOES NOT SUPPORT THE TEXTCONTENT PROPERTY UPDATE

They make this most basic task of maintaining a production SaaS environment very time consuming. I went with this methodДЄfter hitting several roadblocks with other techniques since Microsoft wants a person at a browser navigating to their KB pages. I get the errorВ on the 2nd loop.ДЄrrrhhh! It took an inordinate amount of time and creativity to snag all of the KB numbers, build a URL,В loop through the list while snagging the snippets of info that lets me evaluate whether or not I should accept the patch.

INTERNET EXPLORER 8 DOES NOT SUPPORT THE TEXTCONTENT PROPERTY UPDATE

I have the same error generated from a PowerShell script that automates the capture of KB articles for proposed Windows Update server patches. Pretty sporadic but serious bug in COM Interop or IE on Win 7/2008 and Microsoft might be interested in doing more root cause analysis (I'd be happy to provide more information or a dump file).

Second, I would like to see whether other people have run into this and maybe know more about the root causes. The purpose of this post is to first of all communicate this workaround in case others run into the same issue. Exceptions occur only when I do early-bound first. Just as in my debugger experiment, if my application access the same property early-bound after the late-bound access, no exception is thrown. Uses IDispatch internally for COM objects). The VS debugger is using IDispatch to discover all properties of an examined COM object and to query its property values, so I tried the same programmatically, and lo and behold, I was able to access those properties values in an early-bound fashion (Invoke I concluded thatВ examining the object using the debugger changed something in the state ofВ COM InterOp or even in theВ examined object itself so that the next time early-bound access worked.В I believe that the quick watch mechanism of This time I do not get an exception but the correct value of the property is returned.

Once more I set the 'next statement' to the offending statement and try again.Title, url and tagName properties are all shown correctly in the quick watch window. I use the quick watch in the debugger to examine the object whose property I am trying to access.I set the 'next statement' back to the offending statement and try again.Application throws an exception and breaks into the debugger.Application tries to access url, title or tagName property (early bound, using the respective COM interface).I discovered the workaround the following way: Must be something pretty mysterious happening here. interfaces, to avoid the issue and access these properties in all cases. The only workaround I have found so far is to use late-binding, like 'element.GetType().InvokeMember(.)', instead of early-binding, accessing properties via COM I. The only difference I have noticed that with certain IE versions the issue is occurring sooner and/or in different The issue has been observed with IE 8, 9 and 10. The Internet Explorer version does not seem to play a role, or if anything not a major role.Also, it seems I am not the only one encountering this issue. But having tested the application on a handful of Win 7/2008 machines, Windows XP/2003 does not show this problem! Over many years and on many XP systems, this has never occurred. Important: The issue only occurs on Win7/2008 based OS.The DocumentComplete event was fired, and the ReadyState was Complete. In all cases the page/documents has finished loading.My suspicion is that it is not just these properties that are affected but the whole objects. I have observed the issue when trying to access the HTML document title, document URL, and form element tagname properties.

The issue is not website-specific, it occurs with several websites.

I have only encountered the exception after the browser control has performed one or more subsequent navigations or posts after the initial navigation to a start page.

My investigation showed the followingВ (and also have found a workaround that I will share at the end): More specifically, it is using a customized version of the csEXWB project ( ).

The application is not using the WinForms WebBrowser control but instead creates a 'native' WebBrowser control via Activator.CreateInstance.

Net raises a NotSupportedException with the message:ДЇirst, let me provide some more information about the affected systems and the application: Sometimes when the application accesses properties ofВ IHTMLDocument orВ IHTMLFormElement. In short my problem is the following: A WinForms application hosts one or more web browser controls.

Internet explorer 8 does not support the textcontent property