Telerik blogs

Latest

  • Web ASP.NET AJAX

    Say hello to RadControls Prometheus Futures

    I am glad to announce that we have just released a "Futures" version of RadControls Prometheus. Why "Futures"? I will tell you in detail below, but those of you who are anxious to get their hands on the latest release, can download it from here: http://www.telerik.com/community/forums/thread/b311D-mhkha.aspxWhat's new in the "Futures" release? The highly anticipated RadScheduler. Those of you who had the chance to visit our TechEd booth may have already seen it. For those who haven't - here is a link to the online examples: http://www.telerik.com/demos/aspnet/prometheus-futures/Scheduler/Examples/Default/DefaultCS.aspxKey features: Day, Week and Month View Inline and Advanced editing of appointments Custom resources Recurring appointments Rich client-side behavior The RadScheduler...
  • Web

    Unwanted GET requests with latest IE and FireFox in case of empty img.src, script.src and link.href

    If you create or declare img and script element with empty src attribute or link element with empty href attribute you will receive unwanted GET request with latest FireFox. The problem with img elements exist even in IE 6/ IE 7 however the request will be to the application root. You can check all these using this simple example:<%@ Page Language="C#" %><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><script runat="server">    protected void Page_Load(object sender, EventArgs e)    {    }</script><html xmlns="http://www.w3.org/1999/xhtml"><head id="Head1" runat="server">    <title>Untitled Page</title>    <script src=""></script>    <link href="" /></head><body>    <form id="form1" runat="server">        <img src="" />        <div>        </div>    </form></body></html>You should be extra careful...
  • Web

    An HTML drawing master :-)

    I just came across something amazing... and this is not fake, this is real - you can check the actual...
  • Web

    Never access the controls collection in Page_Init or Page_PreInit with declarative data-binding in ASP.NET 2.0

    If you have a GridView, DataGrid, DetailsView, FormView, DataList or Repeater bound using DataSourceID you should never touch the controls collection in Page_Init or Page_PreInit. If you do this your declarative data-binding will be lost on any outside of the control post-back. How to check this?Example:aspx<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Default.aspx.cs" Inherits="_Default" %><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head runat="server">    <title>Untitled Page</title></head><body>    <form id="form1" runat="server">        <asp:Button ID="Button1" Text="Button1" runat="server" />        <asp:GridView ID="GridView1" AllowPaging="true" DataSourceID="AccessDataSource1"            runat="server">        </asp:GridView>        <asp:DetailsView ID="DetailsView1" DataSourceID="AccessDataSource1" AllowPaging="true"            runat="server">        </asp:DetailsView>        <asp:FormView ID="FormView1" DataSourceID="AccessDataSource1" AllowPaging="true"            runat="server">            <ItemTemplate>                ProductID :                <%# Eval("ProductID") %>            </ItemTemplate>        </asp:FormView>        <asp:DataList ID="DataList1" DataSourceID="AccessDataSource1" runat="server">            <ItemTemplate>               ...
  • Web ASP.NET AJAX

    Firewalls breaking ASP.NET AJAX!

    This one is serious and may bite you any time. Yesterday Shaun posted this problem in our forums: he and his users were experiencing odd errors when requesting ASP.NET AJAX-based sites, and yes, that means RadControls "Prometheus" based ones as well. Partial rendering requests initiated by UpdatePanel controls failed with the cryptic message: ============== Sys.WebForms.PageRequestManagerParserErrorExeption: The message received from the server could not be parsed.  Common causes for this error are when the response is modified by calls to Response.Write(), response filters, HttpModules, or server trace is enabled.  Details:  Error parsing near '<!DOCTYPE html P''. ============== Of course all that comes without any trace of Response.Write(),...