• We are most excited to announce the public availability of our RadControls for Windows 8 Q1 2013 release...
  • In this post I show you how to quickly add the correct HTML/CSS to adhere to Microsoft's Layout Guidelines for Windows Store Applications.
  • As you already know we have introduced new rendering model for RadInput in Q3 2011. It was later set as default mode in Q1 2012.

    The initial idea behind this change was to remove 2 of the input elements from the output HTML of the control and use a span that to overlay the visible one in order to show the formatted value. With this approach we really have fewer elements on the page and in the same time we could show, validate and submit different values. We also removed the table in order to provide better styling potential and boost...

  • The Q1 2012 beta release is out the door and we have some exciting new improvements to brag about. Among everything else is a feature long waited for - client-side databinding for RadListView. In a series of blog posts, I will try to introduce you to the specifics of the client-side databiding with RadListView and give you some insight into the new client cabalities that you can leverage to build performant data bound UI on the client. We will start with a brief introduction to HTML templates, binding expressions and databinding API, we'll go down to databinding to web services and various data sources and will finish off...

  • As we are constantly trying to improve our controls, in Q3 2011 we are introducing new HTML rendering for Telerik’s ASP.NET AJAX Input control – single input rendering. First of all I should assure you that the old rendering is still available, so all your custom styles and complicated scenarios with RadInput will still work.

    Let’s check some of the advantages of the single input rendering mode comes with: 

    • No table is used when having buttons and/or labels, which results in quicker rendering.
    • Less HTML is rendered as a whole, which leads to less data transferred to the client.
    • The control can show readable text when...
  • XML Syntax Rules

    Friday, April 03, 2009 by ASP.NET AJAX Team | Go comment!

    All XML Elements Must Have a Closing Tag

    In HTML, you will often see elements that don't have a closing tag: 

    <p>This is a paragraph 
    <p>This is another paragraph 
     

    In XML, it is illegal to omit the closing tag. All elements must have a closing tag:
    <p>This is a paragraph</p> 
    <p>This is another paragraph</p>  
     

     

     Note: You might have noticed from the previous example that the XML declaration did not have a closing tag. This is not an error. The declaration is not a part of the XML document itself, and it has no closing tag.

    XML Tags are Case Sensitive

    XML elements are defined using XML tags.
    XML tags are case sensitive. With XML, the tag <Letter> is different from the...