search

eldenjh / csexwb2

Automatically exported from code.google.com/p/csexwb2
0 stars 0 forks source link

Member not found #103

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create a new project with a csexwb browser, and set it to navigate to 
homepage (in my case MSN.com)
2. Execute the program
3. For the MSN.com page, Exception happened for several sub urls of the MSN 
homepage.

What is the expected output? What do you see instead?
No crashes, web page should load. I see a Member not found unhandled exception 
in csexwb.cs on the line "IHTMLDocument2 doc2 = (IHTMLDocument2)wb2.Document;"

What are the OS and IE versions?
Windows 7 + IE9
What version of the product are you using?
2.x

Please provide any additional information below.

Is using the .NET framework 4 with VS2010. If i click continue after all the 
exceptions, it works alright. Need to get rid of exception though.

Original issue reported on code.google.com by fullmeta...@gmail.com on 24 Apr 2011 at 10:29

Attachments:

GoogleCodeExporter commented 8 years ago 
SOLUTION: Target .NET 2 instead of .NET 4.

Original comment by fullmeta...@gmail.com on 25 Apr 2011 at 12:49

GoogleCodeExporter commented 8 years ago 
Possible, it's because you click on IFrame. if target IFrame has different 
domain - Document property for it isn't accessible for IE9 only.

Original comment by lobanvik...@gmail.com on 30 May 2011 at 11:32

GoogleCodeExporter commented 8 years ago 
I found out that csEXWB definition of IWebBrowser2 is different from what .NET 
actually generates for you as interop for SHDocVw. See 
http://pinvoke.net/default.aspx/Interfaces/IWebBrowser2.html for full 
definition. I replaced original IWebBrowser2 with this and now I can access 
Document property also in IE9.

Original comment by xkatu...@gmail.com on 16 Jun 2011 at 11:22

GoogleCodeExporter commented 8 years ago 
I think I have had similar issues where sometimes my application could not 
access IHTMLElement.tagName, IHTMLDocument2.url (or Doc3?), 
IHTMLDocument2.title and possibly others. I ended up using the mshtml library 
for all DOM manipulations. 

mshtml.IHTMLDocument2 doc = (mshtml.IHTMLDocument2) 
m_Browser.GetActiveDocument();

After reading xkatu's posting, I suspect it's not just the IWebBrowser2 
interface that has issues but possibly others, too.

Original comment by cbwiena...@gmail.com on 24 Sep 2013 at 5:41