Hi Bruce: It sounds like you are " Source Text scraping" to find elements in the source code unless you are using like the xml dom and features to navigate it.
So I am guessing you use the http request/response or http client models to download the source code. Then you parse the text to find a link and a process command to execute a url once you have parsed it out. I use this technique often myself in vb.net. This requires you to manage the UI of the entire Webpage which is not what I would want to do. If so, I might just create a InternetExplorer object in a vb.net project and then just use the event handlers, objects and dom JavaScripting capabilities to produce the page so it runs normally in my project rather than trying to script the native version of Internet Explorer running on my, or other peoples, machines. There are drawbacks to both methods and I was hoping there was a better work-around but perhaps not. Perhaps developing WE Scripts in JavaSCript might b better but I don't know if JS gets around the problem of single something when the native UIA API and Managed API requires multi something forcing us to create wrappers in another language as Jamal had done. I haven't looked at scripting in some time now since I either find a quick work-around for accessibility issues or, in the case of some programs and Websites, just don't use them. Thanks for the offer to check out your code base but I know exactly what I will find since I do the exact same thing in vb.net but use the built-in objects and event handlers to make coding light years easier. All this said, what you are doing is pretty cool but the next step. Direct interaction with the browsers'objects Event Handlers and properties. Thanks my friend for the offer, I really appreciate it, but been there and done that for over a decade - the technique is burned into this old grey matter like my own name - whatever that is grin. God Bless and good hunting: Rick USA
