Alvo said:
hi,
no, WebBrowser1 is just a standard WebBrowser control. does it work now?
Ah, I see, I thought it might be.
What John Skeet and I were asking about was whether you had written the
entire browser, rendering engine and all. Hence the incredulous "you
wrote an entire browser from scratch????" response, because writing a
fully-featured one from windows sockets to rendered content would be an
enormous challenge. Imagine parsing the HTML stream and then drawing the
document on a blank canvas. Imagine trying to keep it up to date with
new standards. Imagine trying to parse and render sensibly all the
broken HTML out there. Imagine writing a javascript runtime engine. A
cool hobby project for someone with a *lot* of time on their hands, but
frankly, I'd rather be fishing

)
What you've done sounds like a good use of the control, though. Have you
had a go at navigating the document object model from C#? If not, try
this, and have a look at the properties and methods on doc:
mshtml.IHTMLDocument2 doc =
(mshtml.IHTMLDocument2)this.WebBrowser1.Document;