Comments on: A syntax highlighting TextBlock for Silverlight 3

By: Walt

Walt — Sun, 23 May 2010 05:56:20 +0000

This only seems to work with the C# language. whenever I try using other languages I get An unhandled exception of type ‘System.StackOverflowException’ occurred in mscorlib.dll”

By: Vladimir Horbovanu

Vladimir Horbovanu — Thu, 06 May 2010 17:14:19 +0000

I made a demo about creating a simple syntax highlighting TextBox in Silverlight, taking advantage of templates and databinding (the MVVM way). Editing works and the syntax parser can be replaced with a faster / complete one. You can find it here: http://www.vladhorby.com/Blog/post/2010/05/05/Syntax-Highlighting-TextBox-in-Silverlight-using-MVVM.aspx

By: Links (3/14/2010) « Steve Pietrek-Everything SharePoint/Silverlight

Links (3/14/2010) « Steve Pietrek-Everything SharePoint/Silverlight — Mon, 15 Mar 2010 01:12:30 +0000

[...] A syntax highlighting TextBlock for Silverlight 3 [...]

By: Dew Drop – March 10, 2010 | Alvin Ashcraft's Morning Dew

Dew Drop – March 10, 2010 | Alvin Ashcraft's Morning Dew — Wed, 10 Mar 2010 13:26:53 +0000

[...] A syntax highlighting TextBlock for Silverlight 3 (Jeff Wilcox) [...]

By: Morten

Morten — Tue, 09 Mar 2010 16:48:58 +0000

Jack: Duh! I should learn to read blogposts more thoroughly before commenting

By: Jack Bond

Jack Bond — Tue, 09 Mar 2010 02:05:12 +0000

@Morton

It can’t be based on TextBox because it has no formatting. As he pointed out, Silverlight 4′s richtextblock should be the best of both worlds. Highlightable/Copyable, formattable, inputable.

By: Morten

Morten — Mon, 08 Mar 2010 22:38:52 +0000

Btw, I’m getting “An unhandled exception of type ‘System.StackOverflowException’ occurred in mscorlib.dll” when using Xaml or Xml as SourceLanguage. line 59. I don’t think you meant to be calling SetValue again in OnSourceLanguagePropertyChanged. That causes an infinite loop. Also the if condition should probably be using && instead of ||.
Lastly, this check a few lines futher down:
if (e.NewValue != e.OldValue)
shouldn’t really be necessary. They are always different when that method is called (calling setvalue with the same value does not trigger the changedhandler to be called AFAIK).

By: Raghuraman K

Raghuraman K — Mon, 08 Mar 2010 22:31:24 +0000

Good Idea !!! Thank you for posting !!!

By: Morten

Morten — Mon, 08 Mar 2010 21:50:25 +0000

Sweet!
Would be nice if it inherited from TextBox instead, so the user can select parts of the code and copy paste it (I gather this is main reason for having this control).

By: Einar Ingebrigtsen

Einar Ingebrigtsen — Mon, 08 Mar 2010 20:04:39 +0000

Great stuff. Looking good.

I was fiddling a couple of months ago with a similar control, but stopped after a heap of problems with it.

Now I can get syntax highlighting in my Balder samplebrowser..