LinkButton in ListView in UpdatePanel causes full postback

I have a LinkButton in a ListView in an UpdatePanel. I would like the button (well, any of them) to cause a partial postback, but they are causing a full page postback.

<asp:UpdatePanel ID="upOutcomes" UpdateMode="Conditional" runat="server">
  <ContentTemplate>
      <asp:ListView ID="lvTargets" runat="server" onitemdatabound="lvTargets_ItemDataBound">
        <ItemTemplate>
          <asp:LinkButton ID="lnkAddTarget" CssClass="lo" Text='<%# Eval("Title") + " <b>" + Eval("Level") + Eval("SubLevel") + "</b>" %>' runat="server"></asp:LinkButton>
        </ItemTemplate>
      </asp:ListView>
  </ContentTemplate>
</asp:UpdatePanel>

I found another post on stackoverflow which suggested adding this:

protected void lvTargets_ItemDataBound(object sender, ListViewItemEventArgs e) {
  var lb = e.Item.FindControl("lnkAddTarget") as LinkButton;
  tsm.RegisterAsyncPostBackControl(lb);  // ToolkitScriptManager
}

It hasn’t made a difference…

There are a few other similar posts too, but I can’t find a solution! Any ideas?

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

The ClientIDMode setting in ASP.NET 4 lets you specify how ASP.NET generates the id attribute for HTML elements.

In previous versions of ASP.NET (i.e. pre 4), the default behavior was equivalent to the AutoID setting of ClientIDMode. However, the default setting is now Predictable.

Read Microsoft Article

AutoId is required for this because of the way the script manager expects the HTML controls to be generated in previous versions of .NET.

Method 2

I resolved this problem by setting: ClientIDMode="AutoID" on the page directive of the applicable page like so:

<%@ Page Title="" ClientIDMode="AutoID" Language="C#"%>

This is working fine.

Method 3

Try adding CommandName, CommandArgument attributes and the OnCommand event handler to your linkbutton like this:

<asp:LinkButton CommandName='test' CommandArgument='<%# Eval("Title") %>' ID="lnkAddTarget" runat="server" OnCommand="LinkButtonCommandEventHandler" />

Or – adding OnItemCommand handler to the whole ListView.

Method 4

I resolved this problem by setting: ClientIDMode=”AutoID” on the page directive of the applicable page like so:<%@ Page Title="" ClientIDMode="AutoID" Language="C#"%>, thus resolving my previous problem of having an ASP linkbutton within a ListView to cause a full postback.

However, this may require that any ASP control on the client code (Jquery, Javascript) be referred to by it’s full name as it appears in the browser source code (I use Firebug in Firefox to get the names). For example, this Jquery function $("#ContentPlaceHolder1_btnCancelReferCustomer").click(function () {
$("#divRefer").hide({ effect: "slide", duration: 200 });
return false;
});
was changed to this (please note the asp button name change in selector):
$("#ctl00_ContentPlaceHolder1_btnCancelReferCustomer").click(function () {
$("#divRefer").hide({ effect: "slide", duration: 200 });
return false;
});

Method 5

I resolved this problem by setting: ClientIDMode=”AutoID” on the page directive of the applicable page like so:<%@ Page Title=”” ClientIDMode=”AutoID” Language=”C#”%>

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0