Dim WebBrowser1 As New WebBrowser
Dim TRs As HtmlElementCollection = WebBrowser1.Document.GetElementById("table1").GetElementsByTagName("TR")
For Each TR As HtmlElement In TRs
With TR.FirstChild
MsgBox(.InnerText) 'First TD
MsgBox(.NextSibling.InnerText) 'Second TD
more than...
End With
Next

EO.Webbrowser
how to use like MS IE
HtmlElementCollection
GetElementById("table1").GetElementsByTagName("TR")
FirstChild
NextSibling

If even the basic functions must use EvalScript
Why should I spend to buy this software?
Really regret later
can I return it?

Hi,

There are a number of reasons why we use EvalScript:

1. EvalScript is much faster than MS's DOM model. This is because when you use EvalScript, no matter how complicated the expression is, it is done through one round trip to the browser engine. When you use DOM model, it needs to make a round trip to the engine on every property/method evaluation (basically every "." you see in your expression). In the old days everything runs inside your process this different is not obvious. However nowadays all browser engine use multiple processes model for enhanced security. This makes EvalScript much faster;

2. JavaScript represents everything you can do with a web page and interact with the browser's native DOM objects directly. All other programming interface are based on this. So in order to automate a web page sucessfully, you either have to learn JavaScript, or have to learn a separate set programming interface like MS's wrapper classes, which are basically just a duplicates of the browser's native DOM objects. Most of our customers are familar with JavaScript since that's the root of everything. There is no point for us to force user to learn another interface when JavaScript already can do everything;

3. You can do a lot more with JavaScript than with MS' style wrapper class. Web technologies evolves very fast these days and new objects/interface are constantly being added --- all of them are accessible through JavaScript but won't be accessible throw the wrapper classes that you are familiar with unless a new version of the wrapper classes is released.

It's exactly because of these reasons that product like EO.WebBrowser exists and why many users choose our product over MS's built in free webbrowser control. However we do understand that one size won't fit all ---- if you feel more comfortable with MS style classes then it doesn't make sense for you to invest time and effort in our product. We generally do not issue refund in order to avoid fradulent orders, and you have agreed to this policy when you access the license key. However we will make a one time exception for you. Please use the "Contact Us' page to contact us and provide your order number and states the reason you requests the refund. We will process it as soon as we receives it. Your license key will be revoked once the refund is processed.

Thanks!