What is a good alternative to the WPF WebBrowser Control?

I don't think there are many fully-managed web controls. There's an unusual one at modeltext.com/html (I'm its author) This a Windows Forms control, not WPF. The Windows Forms – WPF Interoperability FAQ suggests that's not a problem; but I don't know whether the "airspace problem" precludes using a Windows Forms control On the plus side: Fully managed Performant: low CPU at least (I don't know what your memory requirements are) Can have more than one instance of it in an application On the minus side: Only a subset of the functionality that would be supported by a mainstream browser (so, it depends what you want it for) Beta quality Edit: Looks like nice work Thank you For this application I need a fully functional browser (I must support javascript) In that case, this wouldn't work for you: this control exposes .

NET (not javascript) DOM APIs; so, applications can implement and install DOM event handlers, which are written in C# instead of in javascript And yes, hosting the control in a WPF app will work fine until you need to layer your objects. All winforms controls will suffer from this problem due to the rendering pipelines. See the link above.

Have you considered a native WPF port? A WPF port might be possible, because it renders onto/via an abstract device-context-like interface, of which I have two complete/distinct implementations so far: One uses System.Windows. Forms and System.

Drawing The other is my automated test framework, which implements the 'humble dialog' pattern for GUI regression testing Theoretically perhaps I could implement a third, for WPF, using System.Windows. Controls and System.Windows. Media Kind of random but you might find this interesting: http://blog.spencen.com/2008/01/19/html-to-flowdocument-converter.aspx Thank you for that: I do find that interesting.

The WPF RichTextBox provides a lot of functionality for editing.

I don't think there are many fully-managed web controls. There's an unusual one at modeltext.com/html/ (I'm its author). This a Windows Forms control, not WPF.

The Windows Forms – WPF Interoperability FAQ suggests that's not a problem; but I don't know whether the "airspace problem" precludes using a Windows Forms control. On the plus side: Fully managed Performant: low CPU at least (I don't know what your memory requirements are) Can have more than one instance of it in an application On the minus side: Only a subset of the functionality that would be supported by a mainstream browser (so, it depends what you want it for) Beta quality Edit: Looks like nice work. Thank you.

For this application I need a fully functional browser (I must support javascript). In that case, this wouldn't work for you: this control exposes . NET (not javascript) DOM APIs; so, applications can implement and install DOM event handlers, which are written in C# instead of in javascript.

And yes, hosting the control in a WPF app will work fine until you need to layer your objects. All winforms controls will suffer from this problem due to the rendering pipelines. See the link above.

Have you considered a native WPF port? A WPF port might be possible, because it renders onto/via an abstract device-context-like interface, of which I have two complete/distinct implementations so far: One uses System.Windows. Forms and System.

Drawing The other is my automated test framework, which implements the 'humble dialog' pattern for GUI regression testing Theoretically perhaps I could implement a third, for WPF, using System.Windows. Controls and System.Windows.Media. Kind of random but you might find this interesting: http://blog.spencen.com/2008/01/19/html-to-flowdocument-converter.aspx Thank you for that: I do find that interesting.

The WPF RichTextBox provides a lot of functionality for editing.

Looks like nice work. For this application I need a fully functional browser (I must support javascript). And yes, hosting the control in a WPF app will work fine until you need to layer your objects.

All winforms controls will suffer from this problem due to the rendering pipelines. See the link above. Have you considered a native WPF port?

Kind of random but you might find this interesting: blog.spencen. Com/2008/01/19/html-to-flowdocument-converter. Aspx – VoidDweller May 29 '10 at 18:53 nice work.

Thanks – Sky Sanders Aug 9 '10 at 18:09.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.