OT: Same UserControl on Different Pages, different behavior??

david.wendelken posted on Friday, August 25, 2006

I have a user control that is acting very, very strangely.

Two gridviews on it, nearly identical. Both have a delete button on them, both wired to their respective OnCommand event handlers with structurally identical code.

This control is used in two pages, one directly in the page, one inside a wizard in another page.

In the wizard page, the top grid button works perfectly.

In the standalone page, the top grid button doesn't work unless I add this to the page directive:

EnableEventValidation="false"

If I add the above line, the top grid button works as expected.

That line is not present in the wizard page directive.

Now comes more fun with the bottom grid:

In the stand-alone page, the bottom grid button event handler fires correctly .

(However, the GridView is "empty" whereas in the top grid event handler, the GridView is "full".)

In the wizard page, the bottom grid button event handler never fires at all.

Needless to say, I am really, really, really confused by all this.

Why would the same user control work differently when embedded in different pages? In particular, why would the event handlers work/not work?

From Top Grid:

<asp:TemplateField ShowHeader="False">

<ItemTemplate>

<asp:ImageButton ID="btnBatchDelete" runat="server" CausesValidation="False" CommandName="Delete"

ImageUrl="~/Images/delete.gif"

CommandArgument='<%# DataBinder.Eval(Container,"RowIndex") %>'

OnCommand="gvBatch_DeleteCommand" />

</ItemTemplate>

</asp:TemplateField>

From Bottom Grid:

<asp:TemplateField ShowHeader="False">

<ItemTemplate>

<asp:ImageButton ID="btnDetailDelete" runat="server" CausesValidation="false" CommandName="Delete"

ImageUrl="~/Images/delete.gif"

CommandArgument='<%# DataBinder.Eval(Container,"RowIndex") %>'

OnCommand="btnDetail_DeleteCommandxxx" />

</ItemTemplate>

</asp:TemplateField>

From Top Grid:

protected void gvBatch_DeleteCommand(object sender, CommandEventArgs e)

{

// This button was templated so that it would have its own command handler instead of using

// the GridView RowCommand event handler directly. The reason is due to a known bug.

// At some point, the problem will be fixed and the field could be moved back to a simple command button.

// see http://www.velocityreviews.com/forums/t261419-row-command-firing-twice-in-gridview-control.html

ImageButton btnDelete = (ImageButton)sender;

GridView gv = (GridView)Helper.FindControl(btnDelete.Page,"gvBatch");

int rownum = Convert.ToInt32(e.CommandArgument);

From Bottom Grid:

protected void btnDetail_DeleteCommandxxx(object sender, CommandEventArgs e)

{

// This button was templated so that it would have its own command handler instead of using

// the GridView RowCommand event handler directly. The reason is due to a known bug.

// At some point, the problem will be fixed and the field could be moved back to a simple command button.

// see http://www.velocityreviews.com/forums/t261419-row-command-firing-twice-in-gridview-control.html

ImageButton btnDelete = (ImageButton)sender;

GridView gv = (GridView)Helper.FindControl(btnDelete.Page, "gvDetail");

int rownum = Convert.ToInt32(e.CommandArgument);

The bottom grid shows up empty (it isn't!), and the top grid shows up full (it is).

In the wizard page, the bottom grid event handler doesn't fire. In the stand-alone page, it does.

The wizard page sets the control to invisible if the user options are such that the user won't be allowed to navigate to that page, visible otherwise. Beyond that, neither page has any of my code that would change any user control setting.

OT: Same UserControl on Different Pages, different behavior??

david.wendelken posted on Friday, August 25, 2006

david.wendelken replied on Saturday, August 26, 2006

david.wendelken replied on Tuesday, August 29, 2006