Scintilla.NET is a Windows Forms control, wrapper, and bindings for the versatile Scintilla source code editing component.
- NOTE: I updated the Nuget package name to Scintilla5.NET for those searching the gallery.
"As well as features found in standard text editing components, Scintilla includes features especially useful when editing and debugging source code. These include support for syntax styling, error indicators, code completion and call tips. The selection margin can contain markers like those used in debuggers to indicate breakpoints and the current line. Styling choices are more open than with many editors, allowing the use of proportional fonts, bold and italics, multiple foreground and background colours and multiple fonts." -- scintilla.org
Scintilla.NET can also be used with WPF using the WindowsFormsHost. For Linux, see the Scintilla.NET.Gtk.
- ScintillaLexers - A class library containing lexer definitions for the Scintilla.NET
- VPKSoft.ScintillaUrlDetect - A library to detect URLs with the ScintillaNET control
- VPKSoft.ScintillaSpellCheck - A spell checking library for the Scintilla.NET
- ScintillaDiff - A class library for comparing two text files with the Scintilla.NET control
- ScintillaTabbedTextControl - A tabbed control for Scintilla.NET to display multiple documents
- ScintillaNetPrinting - Add print functionallity to Scintilla.NET
- AutoCompleteMenu-ScintillaNET - Adds an autocomplete menu to ScintillaNET that's more flexible.
- ScintillaNET-FindReplaceDialog project for adding a Find/Replace dialog to ScintillaNET (thanks to @Stumpii)
This project is continuing from the abandoned ScintillaNET by Jacob Slusser and transferred from VPKSoft who has done an incredible job of updating and extending the original project.
Scintilla.NET is in active development. If you find any issues or just have a question feel free to use the Issues feature at our GitHub page. NOTE: I don't read the issues posted to the main fork - so if your issue is about this project, post it here.
Compiled versions which are production ready can be downloaded from NuGet or the Releases page.
For the latest and greatest you can build the Master branch from source using Visual Studio 2022.
Versions before v.5.3.1.1: Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017, 2019, and 2022 is required for the component to work, see #16.
For more information about the history and background information, look at the wiki here.
One of the issues that ScintillaNET has historically suffered from is the fact that the native Scintilla control operates on bytes, not characters. Prior versions of ScintillaNET did not account for this, and when you're dealing with Unicode, one byte doesn't always equal one character. The result was an API that sometimes expected byte offsets and at other times expected character offsets. Sometimes things would work as expected and other times random failures and out-of-range exceptions would occur.
No more. One of the major focuses of this rewrite was to give ScintillaNET an understanding of Unicode from the ground up. Every API now consistently works with character-based offsets and ranges just like .NET developers expect. Internally we maintain a mapping of character to byte offsets (and vice versa) and do all the translation for you so you never need to worry about it. No more out-of-range exceptions. No more confusion. No more pain. It just works.
Another goal of the rewrite was to accept the original Scintilla API for what it is and not try to coerce it into a .NET-style API when it should not or could not be. A good example of this is how ScintillaNET uses indexers to access lines, but not treat them as a .NET collection. Lines in a Scintilla control are not items in a collection. There is no API to Add, Insert, or Remove a line in Scintilla and thus we don't try to create one in ScintillaNET. These deviations from .NET convention are rare, but are done to keep any native Scintilla documentation relevant to the managed wrapper and to avoid situations where trying to force the original API into a more familiar one is more detrimental than helpful.
NOTE: This is not to say that ScintillaNET cannot add, insert, or remove lines. Those operations, however, are handled as text changes, not line changes.
Complete API documentation is included with all of our packages. In addition there is extensive documentation at the project Wiki which has recipes for common tasks and questions. If you're new to ScintillaNET, the Wiki is a good place to get started.
As previously noted in the project charter, great effort has been made to keep the ScintillaNET API consist with the native Scintilla API. As such, the native Scintilla documentation continues to be a valuable resource for learning some of the deeper features.
Generally speaking, their API will map to ours in the following ways:
- A call that has an associated 'get' and 'set' such as
SCI_GETTEXTandSCI_SETTEXT(value), will map to a similarly named property such asText. - A call that requires a number argument to access an item in a 'collection' such as
SCI_INDICSETFORE(indicatorNumber, ...)orSCI_STYLEGETSIZE(styleNumber, ...), will be accessed through an indexer such asIndicators[0].ForeColororStyles[0].Size.
The native Scintilla control has a habit of clamping input values to within acceptable ranges rather than throwing exceptions and so we've kept that behavior in ScintillaNET. For example, the GotoPosition method requires a character position argument. If that value is less than zero or past the end of the document it will be clamped to either 0 or the TextLength rather than throw an OutOfRangeException. This tends to result in less exceptions, but the same desired outcome.