Response.Redire ct triggers Page_Load

[dwclark]

I am having an issue when I trigger a Response.Redire ct, the Page_Load
fires on the page where the Response.Redire ct was called. From what
I've read, this should not happen and the browser should be sent to
page that was passed in teh Response.Redire ct page. The
AutoEventWireup is set to false on all pages. Any help would be
greatly appreciated.

[Joerg Jooss]

Thus wrote dw*****@gmail.c om,

I am having an issue when I trigger a Response.Redire ct, the Page_Load
fires on the page where the Response.Redire ct was called. From what
I've read, this should not happen and the browser should be sent to
page that was passed in teh Response.Redire ct page. The
AutoEventWireup is set to false on all pages. Any help would be
greatly appreciated.

Just to clarify... the page, on which you call Response.Redire ct() is loaded
*again*?

Cheers,
--
Joerg Jooss
ne********@joer gjooss.de

[dwclark]

Yes it is. I can tell this because I put a
System.Diagnost ics.Trace.Write Line(IsPostBack ); in the Page_Load body
and whenever the Response.Redire ct is called, I receive a True in my
output window and then the next page will load.

[Mark Rae]

<dw*****@gmail. com> wrote in message
news:11******** **************@ i39g2000cwa.goo glegroups.com.. .

I am having an issue when I trigger a Response.Redire ct, the Page_Load
fires on the page where the Response.Redire ct was called. From what
I've read, this should not happen and the browser should be sent to
page that was passed in teh Response.Redire ct page. The
AutoEventWireup is set to false on all pages. Any help would be
greatly appreciated.

Let's assume for a second that you've got an <asp:Button> control on a page
with some code behind which includes the Response.Redire ct code.

1) Page loads first time - Postback is false - Page_Load fires

2) User clicks the button - page posts back - Postback is true - Page_Load
fires - code behind button executes and does the Response.Redire ct

You can't stop the Page_Load event from firing - all you can do is wrap its
contents in a if(Page.IsPostb ack) {}

The Page_Load event will always fire regardless of what the rest of the code
on that page subsequently does...

[dwclark]

Thank you for your explanation, however in my Page_Load section I am
dynamically adding buttons from a query I execute on my database. The
problem is, I do not always get the same button or in the same order (a
feature I want), so when they repopulate, if a new button is in the
place of the old button, I get redirected to the new button destination.

[Joerg Jooss]

Thus wrote dw*****@gmail.c om,

Yes it is. I can tell this because I put a
System.Diagnost ics.Trace.Write Line(IsPostBack ); in the Page_Load body
and whenever the Response.Redire ct is called, I receive a True in my
output window and then the next page will load.

Can you post your code?

--
Joerg Jooss
ne********@joer gjooss.de

[Mark Rae]

<dw*****@gmail. com> wrote in message
news:11******** **************@ j33g2000cwa.goo glegroups.com.. .

Thank you for your explanation, however in my Page_Load section I am
dynamically adding buttons from a query I execute on my database. The
problem is, I do not always get the same button or in the same order (a
feature I want), so when they repopulate, if a new button is in the
place of the old button, I get redirected to the new button destination.

Wow! I'd strongly suggest you rethink your page structure...

If you must create buttons dynamically at run time, do it in Page_Init, not
Page_Load...