>>Strange. So something goes wrong between the initialization of the variables and the firing of Page_Init. Does the constructor for the page fire? Ttry adding a constructor and logging it

Public Sub New()
>>        ' Log here
>>    End Sub

>
>When it freezes, the New() is accessed at the base class level but not on the page. So, it gives this:
>
>Id:__Page Framework.WebForm.Initialize() at 7/9/2010 3:47:22 PM
>Id:__Page Framework.WebForm.New() at 7/9/2010 3:47:22 PM
>Id:__Page LevelExtreme.WebForm.Initialize() at 7/9/2010 3:47:22 PM
>
>When it works, it gives this:
>
>Id:__Page Framework.WebForm.Initialize() at 7/9/2010 3:52:43 PM
>Id:__Page Framework.WebForm.New() at 7/9/2010 3:52:43 PM
>Id:__Page LevelExtreme.WebForm.Initialize() at 7/9/2010 3:52:43 PM
>Id:__Page Framework.WebForm.Page_Init() at 7/9/2010 3:52:43 PM
>Id: ShowHeaderStore.aspx.New() at 7/9/2010 3:52:43 PM
>
>So, basically, the page New constructor gets executed after the Page_Init(). So, it doesn't serve any purpose to add a log in there as it is after Page_Init().
>
>But, we can see that the base class new constructor is executed when it freezes.

I assume, from looking at the sequence when it works, that you are not logging the New() of LevelExtreme.WebForm - it would be interesting to know if that fires when it hangs.
I also assume the LevelExtreme.WebForm is derived directly from System.Web.UI.Page ?

Is the line that logs the .Initialize() line the last to execute (i.e It's possible to declare values anywhere in the page - to be sure it would be best to put this at the end of the code so that it only executes after *all* other types are initialized)