WPF HTML Editor Control

Your ViewModels should not care that HTML is involved. BodyHtml, DocumentHtml, and DocumentTitle are real dependency properties that bind two-way by default: BodyHtml="{Binding Draft.Body}" loads the document from your ViewModel and flows edits back as the user types, with UpdateSourceTrigger under your control. The editor drops into an MVVM codebase the way a TextBox does.

The editor uses standard WPF theming: swap a ResourceDictionary and it follows your light mode, dark mode, or corporate design system - no proprietary skin engine, no separate theme format to learn. For teams that need to retemplate end to end, the Source Code License includes the full control source.

Your users will paste from Word and Outlook - the only question is what your database receives. The editor detects Office clipboard content and cleans it automatically: no MsoNormal noise in saved templates, email bodies, or support replies, and no special button for users to remember.

Need stricter rules? The Pasting event is a checkpoint where your own policy runs before anything enters the document.

One screen saves a fragment into a SQL column; another sends a complete document by email. BodyHtml returns the inner body markup, DocumentHtml the full document with head and doctype - both clean, both ready to store or send, no DOM scraping.

HTML5 output is the default, with overrides available for older render targets.

Templates need fields, not fragile hand-typed tokens. The mail-merge API lets your application define placeholders - customer name, invoice number, renewal date - that users insert at the caret and your code resolves at send time. It turns the editor into a template builder for CRM messages, invoices, and notification emails.

Fourteen Hunspell dictionaries are embedded in the control - English (US and GB), German, French, Spanish, Italian, Dutch, Danish, Swedish, Norwegian, Polish, Czech, and Portuguese (Brazil and Portugal) - so there are no dictionary files to ship. Inline red squiggles, dialog checking, and a per-user custom dictionary work out of the box; any OpenOffice dictionary or your own engine plugs in through ISpellCheckerEngine.

Screenshots in tickets, logos in signatures, product shots in templates - images arrive from files, URLs, and the clipboard. Oversized pastes are resized automatically with MaxPastedImageWidth, and EmbedLocalImagesAsBase64() turns local references into portable, self-contained HTML when output leaves the machine.

Everything the toolbar does, your code can do. Focused services keep the API discoverable:

• Content - read, set, transform, and export HTML
• Formatting and Selection - apply styles and inspect what the user selected
• StateQuery - drive your own UI state: bold, undoable, inside a table
• HtmlChanged - dirty flags, save prompts, live previews
• GetEmailMessageWithLocalImagesEmbedded() - a mail-ready message in one call

WPF buyers notice when a third-party toolbar looks blurry beside the rest of the application. Every toolbar icon is a XAML vector path, not a PNG - crisp at 100%, 150%, and 200% scaling, on 4K monitors and per-monitor DPI setups, with Options.ToolbarIconSize offering small, medium, and large sets. The toolbar lives visually inside your WPF application instead of looking like an older component pasted on top.

In a real application Ctrl+S, Ctrl+F, and Ctrl+P already mean something. KeyBindings binds, remaps, disables, or overrides any of 35 editor actions by EditorActionId, so familiar editing shortcuts stay where users expect them - and your application's global commands win whenever they should.

Use the built-in toolbar as shipped, hide commands a role should not see, or add your own XAML buttons beside the standard ones. ToolbarItemOverrider intercepts built-in actions and StateQuery keeps custom UI in sync, so the editor follows your product's rules instead of imposing its own.

Toolbar, tooltips, dialogs, and context menus ship localized in 14 languages - German, French, Spanish, Italian, Dutch, Portuguese, Polish, Czech, Swedish, Danish, Norwegian, and both English variants - one Language property switches everything. Spell-check language is configured separately through SpellCheckOptions.SpellCheckLanguage, because the application shell and the authored content do not always match.

The visual style builder gives users dialog-driven control over fonts, colors, borders, backgrounds, and spacing - more power than plain rich text, with no raw markup in sight. Your own styling pages can sit beside the built-in ones through IEditorStylePage.

Building on Windows Forms instead? A separate WinForms HTML Editor Control exists with its own landing page, documentation, and licensing. Pick the control that matches your UI stack, then test the trial in the application you actually ship.