Hi,

The Windows Forms sample code would be almost exactly the same as WPF sample. EO.WebBrowser has two classes: WebView and WebControl. The WebControl is thin wrapper control that are either for Windows Forms or WPF (there are two different WebControl classes, one is EO.WebBrowser.WinForm.WebControl and one is EO.WebBrowser.Wpf.WebControl). You can find more information about this relationship here:

http://www.essentialobjects.com/doc/6/start/overview.aspx

Pretty much the only thing different between WPF and Windows Forms is how you initialize the corresponding WebControl class. You can find step by step information here:

http://www.essentialobjects.com/doc/6/start/winform.aspx

The real class that you will be working with most of the time is the WebView class. This class is independent to Windows Forms or WPF. Once you get the WebControl into the form, the rest is all about working with the WebView class. That part is unrelated to Windows Forms or WPF. So almost all code you find in the WPF sample will work in your Windows Forms application as well.

There is no direct equivalent to ProgressChanged or WebBrowserNavigatedEventArgs. The corresponding events on WebView are LoadCompleted and LoadFailed event. Most of the time you do not need to handle these events like you do with MS WebBrowser control because we have a simple call like this:

webView1.LoadUrlAndWait(url);

This call will not return until the Url finishes loading. As such there is no need for you to handle ProgressChanged event.

You can find all WebView events here:

http://www.essentialobjects.com/doc/6/eo.webbrowser.webviewevents.aspx

Hope this helps. Please feel free to let us know if you have any more questions.

Thanks!

You are very welcome. Please feel free to let us know if there is anything else.