[This post is part of the developer's manual preview published on this blog. You can find temporary TOC here.]
As it was stated, Sitefinity template parser is almost completely identical to the ASP.NET template parser (and purposefully so). There are, however, some differences between the two and in this article we are going to examine them.Case sensitivity
Sitefinity template parser is case sensitive, which means that this declaration:
<telerik:MessageControl runat="server" ID="messageCtrl"> |
<ItemTemplate> |
<asp:Label ID="messageText" runat="server"></asp:Label> |
</ItemTemplate> |
</telerik:MessageControl> |
<telerik:messagecontrol runat="server" ID="messageCtrl"> |
<itemtemplate> |
<asp:Label ID="messageText" runat="server"></asp:Label> |
</itemtemplate> |
</telerik:messagecontrol> |
No need for casting
One of the nice, built-in things regarding Sitefinity template parser is the fact that you don’t need to explicitly cast the types you use there. Let us consider the proper usage of the property in standard ASP.NET template parser:
<a href="<%= ((Telerik.Events.WebControls.Admin.EventsItemsList)Parent.Parent).ItemEditUrl %>">edit</a> |
<a href="<%= Parent.Parent.ItemEditUrl %>">edit</a> |