I've seen a similar issue when using mshtml.dll
referenced in our .NET projects, but nothing related to this specific situation. I'm suspecting the issue may have some relation to what was said in this thread (.net document write with mshtml) about the coclass missing in my case all related properties/attributes. The specifics here are that I'm using mshtml.HTMLInputElement
and a set of its properties/attributes while parsing a WebBrowser.Document
object:
if (domElement is HTMLInputElement)
{
HTMLInputElement inputElement = (HTMLInputElement)domElement;
if (inputElement.name == null || inputElement.name.Trim() == string.Empty ||
inputElement.name.Contains("/") || inputElement.name.Contains("="))
{
...
}
}
The above works fine under a development PC (VS2008 3.5 SP1) where besides the name
property some other are also being called successfully like type
, etc.., but when the application is installed under Windows 7 which have all required framework pieces, I get the COMException
:
==============
System.Runtime.InteropServices.COMException crossed a native/managed boundary Message=Member not found. (Exception from HRESULT: 0x80020003 (DISP_E_MEMBERNOTFOUND)) Source=mscorlib
ErrorCode=-2147352573 StackTrace: at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData) at mshtml.DispHTMLInputElement.get_name()
======================
None of the calls to properties like name
, type
, are working now. Always the same Interop.COMException
is being thrown. It sounds to me like the same problem explained in .net document write with mshtml.
Does anyone knows a valid workaround for this issue?
User contributions licensed under CC BY-SA 3.0