Re: Master page postback.. !IsPostback doesnt work

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]" <pbromberg@xxxxxxxxxxxxxxxxxxxxxxx> a écrit dans
le message de news: 7234EE1C-7B09-4206-BA3B-728D1DBFFA44@xxxxxxxxxxxxxxxx
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



"anthonykallay@xxxxxxxxxxxxxx" 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




.