Getting rid of the Windows Forms dependencies

Sep 1, 2011 at 8:40 AM
Edited Sep 7, 2011 at 8:16 AM


First of all thank you for a great initiative. There really is a lack of WYSIWYG HTML editors for WPF out there.

I was wondering why you use the Windows Forms WebBrowser inside a WindowsFormsHost. This could create some issues in certain applications, as WinForms controls always end up on top of WPF controls.
It would be very neat if the entire thing was written in WPF without having to rely on the old WinForms components.

Would this be possible?



Sep 6, 2011 at 6:48 PM

I looked at the code a bit and can tell you the most obvious reason is that the winforms version of the web browsser is most .NET friendly as MSFT actually wrote a CLR wrapper around the ActiveX and MSHTML classes used by native webbrowser.   The problem with WPF web browser is that MSFT actually regressed function by only giving us a Un-Wrapped browser.  This means you must use MSHTML to do everything that was once done in .NET... Certainly do-able but is a bit more messy to get up to speed.