Don't you think that choosing '#' as expression delimiter for kendo templates was not the best idea? As Volodymyr pointed, this conflicts with HTML encoding.
Many platforms do HTML encoding very simple (e.g in MVC I write @Localization.Get("aaa")). But I have to remember every time that it would have worked in regular HTML, and not in kendo template HTML. Kendo MVC seem to not have standard extension method for template-encoding (which is strange, although not hard to implement manually). But anyway syntax start looking weird and there is no way to simplify it:
And this string must be copied again and again into every template, every server-included string. Crazy.
It would make much less problems if you used different symbol ('$' maybe, or at least doubled '##'...). It would make situations, requiring additional encoding extreemely rare (although I understand it's not 100% reliable solution, but it's far better than current approach).
Is there any chance you will change that in the near future (maybe support another template type "text/x-kendo-template2")?