Telerik blogs
  • Productivity

    Getting Started with ADO.NET Data Services and Telerik Open Access – Step III

    After we prepared our data service it is time to put some client UI into it. I must apologize in advance as the only UI that I’ve used is a ListBox control, and it looks… well pretty much ugly. The goal was to proof that the whole setup works as expected, not to design a profound UI solution. I am pretty sure that as a follow up, our SilverLight team will enhance the sample to a full-scale integration example very soon.
    December 16, 2008
  • Web ASP.NET AJAX

    HTTP Compression for your ASP.NET AJAX applications

    With our next service pack you will be able to compress your entire AJAX traffic completely codeless with a single web.config setting: ... <httpModules>    <add name="RadCompression" type="Telerik.Web.UI.RadCompression" />  </httpModules>  ...   <!--         The system.webServer section is required for running ASP.NET AJAX under Internet         Information Services 7.0.  It is not necessary for previous version of IIS.     -->    <system.webServer>      <modules>         <add name="RadCompression" type="Telerik.Web.UI.RadCompression" />      </modules>  ... Features: Support for all traditional ajax requests including RadAjaxManager,...
    December 16, 2008
  • Productivity

    Getting Started with ADO.NET Data Services and Telerik Open Access &ndash; Step II

    In my previous post we looked into providing data to the client using ADO.NET Data Services and Telerik OpenAccess. However it is very rare just to present data, as usually some processing is done by the application on the client side, data gets modified and it is pushed back to the server for persistence. With ADO.NET Data Services this is done by implementing the IUpdateable interface by the data context class used on the server. NOTE: We do not implement IExpandProvider at the moment. They say that a picture is worth a thousand words, so same is true for the code – I...
    December 15, 2008
  • Web ASP.NET AJAX

    Don't Use BODY ONLOAD in ASP.NET AJAX Websites

    In the past developers used <body onload="..."> to execute some script as soon as the page is loaded. Nowadays this is rather old-fashioned, no matter how you look at it. What's more, it doesn't work as expected in ASP.NET AJAX websites. Consider the following example:   <body onload="MyFunction()">    <script type="text/javascript">       function MyFunction()     {        var myAjaxControl = $find("myAjaxControlClientID");        myAjaxControl.doSomething();     }    </script>    </body>    The client-side page load event is fired by the browser as soon as all HTML and scripts have been loaded. However, this happens before the controls' client-side instances have been created. As a result, myAjaxControl will be null and the doSomething() method will trigger a Javascript error. So, a lot better approach...
    December 13, 2008
  • Web

    Showing RadToolTip on RadInput input error

    One of the tools in the RadControls for ASP.NET AJAX suite that is getting a lot of attention these days is the RadInput control. More specifically, the RadInputManager. With this "Manager" control, you can easily add validation to any textbox on your page without littering your markup with ASP.NET validator controls. Plus, you'll get a much more dynamic validation experience when you use RadInput instead of the OTB (Out of The Box) ASP.NET validation controls and better page performance (since the manager enables you to save a lot of HTML and JavaScript). One of the other features of the RadInput textboxes, including textboxes...
    December 13, 2008
  • Productivity

    Getting Started with ADO.NET Data Services and Telerik Open Access &ndash; Step III

    After we prepared our data service it is time to put some client UI into it. I must apologize in advance as the only UI that I’ve used is a ListBox control, and it looks… well pretty much ugly. The goal was to proof that the whole setup works as expected, not to design a profound UI solution. I am pretty sure that as a follow up, our SilverLight team will enhance the sample to a full-scale integration example very soon.
    December 16, 2008
  • Web ASP.NET AJAX

    HTTP Compression for your ASP.NET AJAX applications

    With our next service pack you will be able to compress your entire AJAX traffic completely codeless with a single web.config setting: ... <httpModules>    <add name="RadCompression" type="Telerik.Web.UI.RadCompression" />  </httpModules>  ...   <!--         The system.webServer section is required for running ASP.NET AJAX under Internet         Information Services 7.0.  It is not necessary for previous version of IIS.     -->    <system.webServer>      <modules>         <add name="RadCompression" type="Telerik.Web.UI.RadCompression" />      </modules>  ... Features: Support for all traditional ajax requests including RadAjaxManager,...
    December 16, 2008
  • Productivity

    Getting Started with ADO.NET Data Services and Telerik Open Access &ndash; Step II

    In my previous post we looked into providing data to the client using ADO.NET Data Services and Telerik OpenAccess. However it is very rare just to present data, as usually some processing is done by the application on the client side, data gets modified and it is pushed back to the server for persistence. With ADO.NET Data Services this is done by implementing the IUpdateable interface by the data context class used on the server. NOTE: We do not implement IExpandProvider at the moment. They say that a picture is worth a thousand words, so same is true for the code – I...
    December 15, 2008
  • Web ASP.NET AJAX

    Don't Use BODY ONLOAD in ASP.NET AJAX Websites

    In the past developers used <body onload="..."> to execute some script as soon as the page is loaded. Nowadays this is rather old-fashioned, no matter how you look at it. What's more, it doesn't work as expected in ASP.NET AJAX websites. Consider the following example:   <body onload="MyFunction()">    <script type="text/javascript">       function MyFunction()     {        var myAjaxControl = $find("myAjaxControlClientID");        myAjaxControl.doSomething();     }    </script>    </body>    The client-side page load event is fired by the browser as soon as all HTML and scripts have been loaded. However, this happens before the controls' client-side instances have been created. As a result, myAjaxControl will be null and the doSomething() method will trigger a Javascript error. So, a lot better approach...
    December 13, 2008
  • Web

    Showing RadToolTip on RadInput input error

    One of the tools in the RadControls for ASP.NET AJAX suite that is getting a lot of attention these days is the RadInput control. More specifically, the RadInputManager. With this "Manager" control, you can easily add validation to any textbox on your page without littering your markup with ASP.NET validator controls. Plus, you'll get a much more dynamic validation experience when you use RadInput instead of the OTB (Out of The Box) ASP.NET validation controls and better page performance (since the manager enables you to save a lot of HTML and JavaScript). One of the other features of the RadInput textboxes, including textboxes...
    December 13, 2008