Syntax Highlighting
The easiest way to get syntax highlighting to work is to set the ConfigrationManager.Language property. The list of languages that have been fully configured for syntax highlighting are as follows
Language value | Description |
asm | Assembly |
cs | c# |
html | HTML |
js | JavaScript |
mssql | Microsoft flavored T-SQL |
psql | Postgre SQL |
python | Python |
vbscript | VB Script |
xml | XML |
You can also use any of Scintilla's built in lexer names, however your mileage will vary on these without a full configration specifying all the styles. However many of the lexers use the same styles so try it out and see which syntaxes get highlighted. Note that you'll need to supply keywords for most languages.
ada | d | lot | props |
apdl | diff | lout | ps |
asm | eiffel | lua | purebasic |
asn1 | eiffelkw | make | python |
au3 | erlang | matlab | rebol |
ave | errorlist | metapost | ruby |
baan | escript | mmixal | scriptol |
bash | f77 | mssql | smalltalk |
batch | flagship | nncrontab | specman |
blitsbasic | forth | nsis | spice |
bullant | fortran | null | sql |
caml | freebasic | octave | tads3 |
clw | gap | opal | tcl |
clwnocase | gui4cli | pascal | tex |
cmake | haskell | perl | vb |
conf | hypertext | phpscript | vbscript |
cpp | innosetup | plm | verilog |
cppnocase | kix | pov | vhdl |
csound | latext | powerbasic | xml |
css | lisp | progress | yaml |
ConfigurationManager.Language can either be set in the designer or at runtime through code.