I have noticed that in mojoPortal code most of operations like setting strings from resources to module controls are performed in Page_Load().
And all of them are performed on each postback.
Why not moving them to Page_Init()?

http://msdn2.microsoft.com/en-us/library/ms178472.aspx

"Init: Raised after all controls have been initialized and any skin settings have been applied. Use this event to read or initialize control properties."

You seem to be right:

http://msdn2.microsoft.com/en-us/library/system.web.ui.control.init.aspx
"Server controls should perform any initialization steps that are required to create and set up an instance."
"You should not access another server control during this event, regardless of whether it is a child or parent to this control. Other server controls are not certain to be created and ready for access."

As far as you know, Page is also System.Web.UI.Control.
So, in Page_Init the page itself is guaranteed to be initialized, but all the child controls are not. They are only when Page.InitComplete event is raised.

I did not know this - I used Page_Init to initialize page controls in many projects and never had problems. May be, it is implementation specific (all these projects were Windows-based).


The reason to move setting of labels to Page.InitComplete (not Page.Init) event hadler is that in this case this code will not be executed on postbacks with no need of viewstate.
Of course, the code is working now. But not in the most efficient way. :)