NOTICE: As of 10/28/2017, a new version is available.
Includes the following features:
- Requires .NET 4.5.1.
- Fixes save as and load bugs that fired browser dialogs.
- Insert inline images either by URL or through the file system. File system images are embedded in the resulting HTML.
- Full programmatic access to HTML, Body HTML, Body Text
- Set the background color of the body.
- Insert images.
- Resize images.
- Add and edit hyperlinks from text.
- Add and edit hyperlinks from images.
- Support for Windows XP SP2 to Windows 8.
- Support for all versions of IE.
A while ago, I was working on a chat application where one of the chat clients was web based and written with ASP.NET 2.0. The other chat client was a Windows Forms based .NET application written in C#. I needed a rich text editor for my WinForms client that could output HTML, so that the ASP.NET client could display the formatting from the WinForms client. This was ruled out while using the RTF text box.
The solution I worked out was to use a
WebBrowser control in edit mode within my WinForms client. Formatting buttons on a toolbar above the web browser are synchronized to the current selection in the
This article explains solutions to most of the issues involved in building an editor control from a
WebBrowser control. I won't go into everything, as the source code isn't that difficult to browse. But, I do cover some of the tricks necessary to get this to work.
Using the Control
The control is an executable.
You can run it directly with it's main form, or you can embed it as a control in your own app.
To embed it into your own app, simply reference the EXE as if it were a DLL from your app in Visual Studio.
It should show up in the Toolbox Window in Visual Studio.
Check the source code for examples of how to access it from your code.
It's a .NET 2.0 control, so it should work in older projects.
Setting Design Mode
Applying design mode and establishing an editing template for the document occurs automatically when using the component. But, for reference, here is a brief explanation of how it works.
Applying design mode requires using a COM interface: adding a reference to "Microsoft HTML Object Library", which resolves to MSHTML, and adding a 'using' of 'MSHTML'.
It is necessary to add a body to the control before you can apply changes to the DOM document. To do this, you can simply apply some text to the
DocumentText property of the
webBrowser1.DocumentText = "<html><body></body></html>"
Next, get a reference to the new
DomDocument COM interface, and set the design mode to "
IHTMLDocument2 doc =
webBrowser1.Document.DomDocument as IHTMLDocument2;
doc.designMode = "On";
Finally, I replace the context menu for the web browser control so the default IE browser context menu doesn't show up.
The browser is now in design mode, with a custom method to display the context menu.
You can apply formatting and editor functions to a browser control in design mode with the
ExecCommand method on
Here are several examples:
public void Cut()
webBrowser1.Document.ExecCommand("Cut", false, null);
public void Paste()
webBrowser1.Document.ExecCommand("Paste", false, null);
public void Copy()
webBrowser1.Document.ExecCommand("Copy", false, null);
Some commands will toggle the formatting state of the current selection.
public void Bold()
webBrowser1.Document.ExecCommand("Bold", false, null);
public void Italic()
webBrowser1.Document.ExecCommand("Italic", false, null);
Synchronizing Formatting Buttons with Selected Text
This is a bit more tricky than applying formatting commands to the browser control. I literally query the state of the browser editor selection every 200 ms, and set the toolbar formatting buttons based on this.
private void timer_Tick(object sender, EventArgs e)
boldButton.Checked = IsBold();
italicButton.Checked = IsItalic();
underlineButton.Checked = IsUnderline();
orderedListButton.Checked = IsOrderedList();
unorderedListButton.Checked = IsUnorderedList();
linkButton.Enabled = SelectionType == SelectionType.Text;
if (Tick != null) Tick();
You'll notice that there is a
Tick event that is fired at the end of the timer's tick event. External components can subscribe to this event to update the state of their GUI. For example, they may update the
Enabled state of cut/copy/paste/undo/redo buttons based on the state of the Editor control.
I do this by using the COM document interface retrieved from the
WebBrowser control with:
IHTMLDocument2 doc = webBrowser1.Document.DomDocument as IHTMLDocument2;
Then I use
queryCommandState to determine the state of the current selection:
public bool IsBold()
public bool IsItalic()
public bool IsUnderline()
The link button and font controls are managed in a similar way, but I'll leave that for you to check out in the code.
Focusing the control isn't necessarily simple either. The
WebBrowser control itself will not accept focus. Neither will the
WebBrowser control's document. But, the
body will focus, assuming there is a
body element on the control.
private void SuperFocus()
if (webBrowser1.Document != null &&
webBrowser1.Document.Body != null)
Of course, you never need to call this method directly. Calling the
Focus method on the control will place the focus on the editor control containing the
WebBrowser control. The editor control will transfer focus to the
WebBrowser's document body automatically, when it receives the
Retrieving Text or HTML
BodyText methods retrieve the body HTML and text, respectively.
Linking to the Component Assembly
In Visual Studio 2005, you can link to an assembly (add a reference), even if the assembly is an executable. The editor is written as a component embedded in a form, so you can add this component to the control palette and drag and drop into your application. The control's name is
Editor, under namespace
The .NET 2.0
WebBrowser control can effectively be used as a text editor. This is useful when you need an editor control that can be used as an HTML editor. The implementation is not completely straightforward in some areas. This article attempts to show some of the tricks necessary to get it to work.
- 10/04/2006 - various bug fixes and design updates / designer support.
- 10/19/2006 - more bug fixes and more designer support.
- 10/28/2017 - Upgrade to .net 4.5.1 and VS 2015