Here\'s the code from the ascx that has the repeater:
A sub-he
You need to handle the ItemCommand event on your Repeater. Here's an example.
Then, your button clicks will be handled by the ListOfEmails_ItemCommand method. I don't think wiring up the Click or Command event (of the button) in ItemDataBound will work.
If you're planning to use ItemCommand event, make sure you register to ItemCommand event in Page_Init not in Page_Load.
protected void Page_Init(object sender, EventArgs e)
{
// rptr is your repeater's name
rptr.ItemCommand += new RepeaterCommandEventHandler(rptr_ItemCommand);
}
I am not sure why it wasn't working for me with this event registered in Page_Load but moving it to Page_Init helped.
You know what's frustrating about this?
If you specify an OnClick in that asp:Button tag, the build will verify that the named method exists in the codebehind class, and report an error if it doesn't... even though that method will never get called.
Here's an experiment for you to try:
Set a breakpoint on ListOfEmails_ItemDataBound and see if it's being called for postbacks.
Controls nested inside of Repeaters do not intercept events. Instead you need to bind to the Repeater.ItemCommand
Event.
ItemCommand contains RepeaterCommandEventArgs which has two important fields:
So, a trivial example:
void rptr_ItemDataBound(object sender, RepeaterItemEventArgs e)
{
if (e.Item.ItemType == ListItemType.AlternatingItem || e.Item.ItemType == ListItemType.Item)
{
// Stuff to databind
Button myButton = (Button)e.Item.FindControl("myButton");
myButton.CommandName = "Add";
myButton.CommandArgument = "Some Identifying Argument";
}
}
void rptr_ItemCommand(object source, RepeaterCommandEventArgs e)
{
if (e.CommandName == "Add")
{
// Do your event
}
}