Why does the *.aspx page for the content placeholder in my master page execute it's Page_Load() procedure prior to my Master page's Page_Load() procedure. Sensically it should be the other way around, no?
I'm going to tiddle with the "New" procedure and see how that and the Page_Load() procedure between pages relates to eachother. But in the mean time, does anybody know why Microsoft decided to do this??
ahhh mere mortal do you question the wisdom of the dot NET gods. Yours is to obey and live by they life cycle.
Consider this your first warning, and your first born will be spared.
Of course I agree with your point, but I would never question otherwise my head would hurt, and then some bright spark will ask why we have UserControl_RenderControl() and UserControl_Render(), and the horrible explanations start all over again. SirKilljoy lives in ignorance, and is happy.
Because your master page is actually a glorified user control, not some sort of special page. Go read K Scott Allen's excellent intro to master pages for details.
I see... So my page Loads and then the content placeholder control wrap is oloaded and the Masterpage's Page_load is then executed... Thanks. Now I can fix my problem.
This board needs some kinda rep/thank you feature.
I was wondering about this myself after ordering my new ide and playing around with the trial to get used to new stuff. But it makes sense, since your loading and page which then goes "oh hey, there's a master i need to use..." rather than the other way around.
Posting Permissions
Bookmarks