I'm looking for the way to stop a postback event's method from fireing.

Let's say I have an ImageButton and a Button. Both with their own onClick events set.  During a postback I want to arbitrarily cancel the controls "on click" event from fireing before it hits it.

So, If someone clicks on my IMageButton, I might want to say in the PageLoad; "Ok, continue processing this page like it was just a regular postback without hitting the "onImageButton_Click" event.

Is this possible?

Seeing ASP.NET knows what control initiated the postback, and where it needs to go after the page load, this should be a peice of cake.... But I have searched and searched. Not luck.

 Any thoughts?
 

Hey,

Page_Load fires before the button click, so my thought is have a private variable as such:

private bool _doProcessing = false;

In page load, have your logic to determine whether you need the button click, and in the button handler, do:

if (!_doProcessing)
  return;

which exits the routine and avoids processing the button click.

 That is possible, the boolean would need to be on the root page. I'm unfortunately using the WebSite project which doesn't allow me to directly cast the page as controls/parents in different directories...  but I do have a base "baesPage" which all pages inherit that I could cast my page as that, and use the property on that page.

The only problem with that is on every event I'll need a if(!_doProcessing), which is why I was wondering if I could find where ASP.NET holds the events so i could just say to the postback event "DIE DIE DIE!".  :)

 If I can't you're sugestion is a solid one. Thanks.
 

Hey,

I believe button events use the __EVENTTARGET form property to store the reference to the control that cause the event.  If you wipe that out; though the reason I wonder about that is because that property gets set as the postback occurs, and so I think the server knows about it before you would be able to do anything about it.  I don't know if there is another way.

 Hmm, Yea. Looking at that property it's always "". IT's kinda sad I can't interact with the event process at all to change what's going to get hit :|

Page has button 'A' and 'B'. User clicks 'A'. Postback code begins to execute for 'A'. You want to prevent user from clicking 'B' before 'A' completes its postback? Am I understanding you correctly?

The 2 buttons were just an example.

Pretty much I have code that runs every time a postback/ajax calback takes place. I am looking for a way to keep the postback, but stop any events from the sender from fireing. ex. If someone changes a dropdown list with Autopostback=true on it, I would like to find the place where that event is held and stop it from processing... basically jsut do the page lifecycle over again without going to any Events from any control.  

Hi,

My solution is maybe too simple, but can you use the OnClientClick event. Then you may use javascript ...

At the bottom of your Page_Load event you could add something like this:

if (Page.IsPostBack)
{
    this.Button1.Click -= new EventHandler(Button1_Click);
    this.DropDownList1.SelectedIndexChanged -= new EventHandler(DropDownList1_SelectedIndexChanged);
}

Since Page_Load occurs just before the control events fire, it should stop the control event code from running but still allow the Page_Load method to execute. The removal of the event methods would have to be added for each control that causes a postback.

For a simpler example that could be true. However my pages are dynamically created with a wide array of controls and postbacks. A user could say he wants 500 dropdown lists on a page, and all of them to have a postback event.

In some cases, I want to (on the page load/init/pre init) to take all those "control events/Page events" and delete them. 

RTernier, did you find a solution to this? I have a base page class which i use to check for session timeouts which works fine using standard ASP.NET events. However, when an AJAX event is fired and the session has expired the base page load event correctly determines that the page has expired, but the server side code behind the AJAX event is fired anyway. I don't want to have to put code in to each event that i write to check for the session timing out. i just want prevent the server side code from running and display a popup to the user explaining what happened. Do you know if this is possible?