Multiple page load happens on one ASPX page

- There may be some Response.Redirect in code recursively redirecting
to itself.
- There may be some javascript tied to client-side onload event of
body or some image recursively posting back again and again.
- In VS 2003, AutoEventWireup="true" used to get conflict if during
design you unknowingly had double-clicked a control. However in that
scenario it used to be max two calls.
- Although you explicitly mentioned its an aspx, an ascx may have
Page_Load called multiple times if there are multiple instances on
same page.

- There may be some Response.Redirect in code recursively redirecting
to itself (either directly in same file, or via some other code
suscribing to your code's structured events or bubble events).

- There may be some javascript tied to client-side onload event of
body or some image recursively posting back again and again.

- In VS 2003, AutoEventWireup="true" used to get conflict if during
design you unknowingly had double-clicked a control. However in that
scenario it used to be max two calls, not three.

- Although you explicitly mentioned its an aspx, an ascx may have
Page_Load called multiple times if there are multiple instances on
same page.

On Mar 10, 12:14 am, "Muhammad Naveed Yaseen" <mnyas...@gmail.com>
wrote:

- There may be some Response.Redirect in code recursively redirecting
to itself (either directly in same file, or via some other code
suscribing to your code's structured events or bubble events).

- There may be some javascript tied to client-side onload event of
body or some image recursively posting back again and again.

- In VS 2003, AutoEventWireup="true" used to get conflict if during
design you unknowingly had double-clicked a control. However in that
scenario it used to be max two calls, not three.

- Although you explicitly mentioned its an aspx, an ascx may have
Page_Load called multiple times if there are multiple instances on
same page.

Thank you for the reply. I will re-exam my code with these
possibilities.