There are two Microsoft posts about "How to Create an HTML Editor Application" and "Creating Editable Web Pages in Internet Explorer 5.5
" (Links below).

Without "getting librarian" on me, could you explain to me in non-techical language what's the benefit of using the "HTML Editor" control over using the .Net WebBrowser (or similar) control and taking the MS approach?


Links:
-----

[msdn.microsoft.com]

[msdn.microsoft.com]

These links address a slightly different need, which is creating an editor within a web page. The HtmlEditor is for embedding an HTML Editor in a Windows Forms application. There are other ways to do this too. The reasons for this particular control were:

- To host mhtml without using Axhost (which has some known issues).
- To make it easy to load and read back HTML without going via a file.
- To make it easy to use some of the more advanced features of Mshtml such as print templates, edit designer
- To explore COM interop with .Net

There is a .Net wrapper for the web browser control in Whidbey although I understand this will not directly support editing features (although there may be a way, who knows?)

Tim



Post Edited (11-19-03 23:42)

Thanks, Tim, for your answer. What I understand you're saying is that I get the "meat" without the Cholesterol :-)

My goal is to use this control to supports user-editing. Three more quesions:

1. Does it support Hebrew? How?

2. Does it support Undo/Redo? How?

3. Pros/Cons vs. using an RTF Edit control.

Avi