Hi all,

Just wondering, on my first request to a protected page, whereby the login screen comes up, i see the following order of events

aspx.page Begin Init
 In Derived OnInit 0.000697 0.000697
 In SitePage OnInit 0.001714 0.001017
aspx.page End Init 0.002163 0.000449
 In Derived PageLoad 0.002942 0.000779
 In SitePage PageLoad 0.004038 0.001096
 In Derived PageLoad 0.004109 0.000071
aspx.page Begin PreRender 0.004157 0.000048

Instead of the expected:

Derived OnInit -> PhilePage OnInit -> PhilePage PageLoad -> Derived PageLoad

I believe my event handlers are being wired in the proper order in the derived page:


Protected Overrides Sub OnInit(ByVal e As EventArgs)
         Trace.Warn("In Derived OnInit")
         MyBase.OnInit(e)
         InitializeComponent()
      End Sub


      'This call is required by the Web Form Designer.
      <System.Diagnostics.DebuggerStepThrough()> _
      Private Sub InitializeComponent()
         AddHandler Me.Load, AddressOf Page_Load
      End Sub

After this first request, everything runs as expected. Anyone else encountering a similar situation?

Jake

hello again....acually, the execution order is not as expected on other pages as well b/c when the user tries to access a protected page, thier Principal is not loaded b/c the PhilePage PageLoad event hasn't fired yet! It is doing the same thing as before:

Derived OnInit -> PhilePage OnInit -> Derived PageLoad -> PhilePage PageLoad -> Derived PageLoad

please help!

All,

I think I have discovered the reason for this madness. If we follow the reccomendation of having this code in our derived pages:

'This call is required by the Web Form Designer.
      <System.Diagnostics.DebuggerStepThrough()> _
      Private Sub InitializeComponent()
         AddHandler Me.Load, AddressOf Page_Load
      End Sub

Then be sure to removed the 'handles MyBase.Load' from your Page_Load methods...which the designer automatically creates for you when you create a new web form. I am sure a similar fix exists for the C# version.

Jake