Master page postback.. !IsPostback doesnt work

[anthonykallay]

Hi there,

I dont this this a bug but i cant get my head around it.. I have a
master page that has a login control on it, to log in i press the
button and the page posts back, however on the page that is derived
from the master page (default.aspx) i have code that i dont want to
run after the login button is pressed so i used the standard

if(!Page.IsPost Back) {}

to try and hide the code on default.aspx, however since the postbsck
comes from the control in the master page this code still runs???

How do i stop this code running in default.aspx whn the login button
in the aster page is clicked??

Cheers
Anthony

[Mark Rae [MVP]]

<an***********@ googlemail.comw rote in message
news:11******** **************@ o61g2000hsh.goo glegroups.com.. .

Hi there,

I dont this this a bug but i cant get my head around it.. I have a
master page that has a login control on it, to log in i press the
button and the page posts back, however on the page that is derived
from the master page (default.aspx) i have code that i dont want to
run after the login button is pressed so i used the standard

if(!Page.IsPost Back) {}

to try and hide the code on default.aspx, however since the postbsck
comes from the control in the master page this code still runs???

How do i stop this code running in default.aspx whn the login button
in the aster page is clicked??

A couple of things...

Firstly, in the MasterPage / ContentPage scenario, content pages aren't
"derived" from master pages - quite the reverse! In fact, a MasterPage is
really nothing more than a UserControl.

Secondly, master pages are intended to provide common look and feel (and
sometimes functionality) across several pages, possibly an entire site. If
you have functionality in your master page which is intended for only one
content page, then that functionality would be better placed in the content
page itself, not the master page...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net

[anthonykallay]

Hi Mark,

Thanks for your reply but i dont think you quite understood what my
problem was..

The user control in the master page (login.ascx) does need to be on
every page, the only problem i have is that when i click this login
button and the page posts back all the code in default.aspx page_load
posts again even if i use the !IsPostback statement?? Why is this flag
not stopping the page_load code from executing in the default.aspx
page??

Anthony

[=?Utf-8?B?UGV0ZXIgQnJvbWJlcmcgW0MjIE1WUF0=?=]

A "Postback" is a re-request (via HTTP POST) of the page, which means that
everything - page and MasterPage get reloaded. So if this behavior is giving
you issues, you need to re-think your logic to accomodate.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder( BETA): http://www.blogmetafinder.com

"an***********@ googlemail.com" wrote:

Hi Mark,

Thanks for your reply but i dont think you quite understood what my
problem was..

The user control in the master page (login.ascx) does need to be on
every page, the only problem i have is that when i click this login
button and the page posts back all the code in default.aspx page_load
posts again even if i use the !IsPostback statement?? Why is this flag
not stopping the page_load code from executing in the default.aspx
page??

Anthony

[Patrice]

You could also write the value to make sure your assumption is correct. For
now I would write down the value to make sure it's incorrect. Actually for
now I would expect that the value is correct but that you do something that
doesn't need the code to run (for example when you postback, control values
are populated from posted values even if you don't bind data etc...)

---
Patrice
"Peter Bromberg [C# MVP]" <pb*******@yaho o.yabbadabbadoo .coma écrit dans
le message de news: 72************* *************** **...icrosof t.com...

>A "Postback" is a re-request (via HTTP POST) of the page, which means that
everything - page and MasterPage get reloaded. So if this behavior is
giving
you issues, you need to re-think your logic to accomodate.
-- Peter
Site: http://www.eggheadcafe.com
UnBlog: http://petesbloggerama.blogspot.com
BlogMetaFinder( BETA): http://www.blogmetafinder.com

"an***********@ googlemail.com" wrote:

>Hi Mark,

Thanks for your reply but i dont think you quite understood what my
problem was..

The user control in the master page (login.ascx) does need to be on
every page, the only problem i have is that when i click this login
button and the page posts back all the code in default.aspx page_load
posts again even if i use the !IsPostback statement?? Why is this flag
not stopping the page_load code from executing in the default.aspx
page??

Anthony

[anthonykallay]

Hi all,

Thanks for your replies but i still think im not being clear.. on
default.aspx i have the following code

if (!Page.IsPostBa ck)
{
string page;

if (Request.QueryS tring["PageID"] != null)
page = Request.QuerySt ring["PageID"].ToString();
}

Obviously this code runs the first time the page loads, then when
someone logs in they press the submit button in the login control on
the masterpage causing the page to "postback". However when this
"postback occurs the above code runs when i thought the if (!
Page.IsPostBack ) would stop the code running as i have just posted the
page from the login ox.. Why does this code run??

Cheers
Anthony

[Patrice]

Well have you tried to display Page.IsPostBack as asked previously ? How do
you know for sure that this code runs. Sorry for being picky but sometimes
we start from the assumption that a portion of code runs when actually it is
some other portion that does the job or because the code doesn't need to run
to get the same effect....

I would like to make 100% sure that IsPostBack doesn't return the correct
value. The best way is to just print this value to see wether or not it is
false. You could also dump Request.ServerV ariables("HTTP_ METHOD") to see if
it"'s GET or POST.

For example if you have some other code that does a redirect once the
postback for login occurs (which is perhaps the case with the standard
RedirectFromLog in method) then you would have a postback that does a
redirect and finally you are not seeing a postback in your code (i.e. you'll
see postback being false and the method being GET)...

--
Patrice
<an***********@ googlemail.coma écrit dans le message de news:
11************* *********@n60g2 00...legr oups.com...

Hi all,

Thanks for your replies but i still think im not being clear.. on
default.aspx i have the following code

if (!Page.IsPostBa ck)
{
string page;

if (Request.QueryS tring["PageID"] != null)
page = Request.QuerySt ring["PageID"].ToString();
}

Obviously this code runs the first time the page loads, then when
someone logs in they press the submit button in the login control on
the masterpage causing the page to "postback". However when this
"postback occurs the above code runs when i thought the if (!
Page.IsPostBack ) would stop the code running as i have just posted the
page from the login ox.. Why does this code run??

Cheers
Anthony