Best practices around "Page_PreRender" and "Page_Load" events - DOTNET

This is a discussion on Best practices around "Page_PreRender" and "Page_Load" events - DOTNET ; Hi, Are there any best practices or recommendations around using "Page_PreRender" vs "Page_Load"? We are thinking to completely switch to Page_PreRender event to handle page's controls initialization requirements. I went through some asp.net page life cycle documentations (and diagrams) and ...

+ Reply to Thread
Results 1 to 8 of 8

Best practices around "Page_PreRender" and "Page_Load" events

  1. Default Best practices around "Page_PreRender" and "Page_Load" events

    Hi,

    Are there any best practices or recommendations around using
    "Page_PreRender" vs "Page_Load"? We are thinking to completely switch to
    Page_PreRender event to handle page's controls initialization requirements.

    I went through some asp.net page life cycle documentations (and diagrams)
    and it seems that we can safely move all Page_Load codes to Page_PreRender.
    Is there any work that we can only do in Page_Load and cannot do it in
    Page_PreRender?

    A link to an online article would greatly help.

    Thank you,
    Max



  2. Default Re: Best practices around "Page_PreRender" and "Page_Load" events

    only if the logic belongs there. the simplified cycle is:

    oninit - use to init controls before postback data loaded

    onload - after postback data applied to controls

    onclick/etc - server events fired

    prerender - after server events

    render - produce html

    general control init should be done in oninit. onload is used if
    controls use viewstate (bad practice - should only be done with
    intranets) or for postback data handling.


    -- bruce (sqlwork.com)


    Max2006 wrote:
    > Hi,
    >
    > Are there any best practices or recommendations around using
    > "Page_PreRender" vs "Page_Load"? We are thinking to completely switch to
    > Page_PreRender event to handle page's controls initialization requirements.
    >
    > I went through some asp.net page life cycle documentations (and diagrams)
    > and it seems that we can safely move all Page_Load codes to Page_PreRender.
    > Is there any work that we can only do in Page_Load and cannot do it in
    > Page_PreRender?
    >
    > A link to an online article would greatly help.
    >
    > Thank you,
    > Max
    >
    >


  3. Default RE: Best practices around "Page_PreRender" and "Page_Load" events

    Hi Max,

    Besides Bruce's input, here's my thoughts on this:

    * Initialization code that runs in first page load (non-postback) is
    normally in Page_Load (http://support.microsoft.com/kb/317794)

    * Normally you need to register client script in PreRender (<<Developing
    Microsoft ASP.NET Server Controls and Components>>, chapter "Client Script
    - Related API"; and this also applies when you're using AJAX:
    http://weblogs.asp.net/leftslipper/a...00_-Write-cont
    rols-compatible-with-UpdatePanel-without-linking-to-the-ASP.NET-AJAX-DLL.asp
    x)


    Hope this helps.


    Regards,
    Walter Wang (wawang@online.microsoft.com, remove 'online.')
    Microsoft Online Community Support

    ==================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ==================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.


  4. Default RE: Best practices around "Page_PreRender" and "Page_Load" events

    Hi Max,

    I'm writing to check the status of this post. Please reply to let us know.
    Thanks.


    Regards,
    Walter Wang (wawang@online.microsoft.com, remove 'online.')
    Microsoft Online Community Support

    ==================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ==================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.


  5. Default Re: Best practices around "Page_PreRender" and "Page_Load" events

    Hi Walter,

    Your response helped me; however I was looking for an actual best practices
    guidelines. From you post I have a feeling that there is no official
    guideline?

    Thank you,
    Max



    "Walter Wang [MSFT]" <wawang@online.microsoft.com> wrote in message
    news:qRWgrm$zHHA.4200@TK2MSFTNGHUB02.phx.gbl...
    > Hi Max,
    >
    > I'm writing to check the status of this post. Please reply to let us know.
    > Thanks.
    >
    >
    > Regards,
    > Walter Wang (wawang@online.microsoft.com, remove 'online.')
    > Microsoft Online Community Support
    >
    > ==================================================
    > When responding to posts, please "Reply to Group" via your newsreader so
    > that others may learn and benefit from your issue.
    > ==================================================
    >
    > This posting is provided "AS IS" with no warranties, and confers no
    > rights.
    >




  6. Default Re: Best practices around "Page_PreRender" and "Page_Load" events

    Hi
    What we usually do here is the following :

    /*************/
    In Page_Load : We put the initialization for the objects (like the object
    holding the logged user's infos) the postback events and pre render will
    need. No display related stuff here because it may be changed by the server
    events. Actually, we could move almost all the code from here to OnInit, but
    we are doing it in Page_Load just to make it all in one place. Actually, the
    only reason I see to put this stuff in the Page_Load is if you depend on
    data from your page like a hidden field or something (to know where you're
    at, like the id of what you are editing)
    /*************/
    In PreRender : It's like "Ok, I'm in that exact state, so what do I display
    and how do I display it?"
    /*************/

    These are not "official" guidelines, but it works pretty well in all
    situations.

    I hope it helps

    ThunderMusic

    "Max2006" <al****an1@newsgroup.nospam> wrote in message
    news:uAounYUzHHA.3908@TK2MSFTNGP05.phx.gbl...
    > Hi,
    >
    > Are there any best practices or recommendations around using
    > "Page_PreRender" vs "Page_Load"? We are thinking to completely switch to
    > Page_PreRender event to handle page's controls initialization
    > requirements.
    >
    > I went through some asp.net page life cycle documentations (and diagrams)
    > and it seems that we can safely move all Page_Load codes to
    > Page_PreRender. Is there any work that we can only do in Page_Load and
    > cannot do it in Page_PreRender?
    >
    > A link to an online article would greatly help.
    >
    > Thank you,
    > Max
    >




  7. Default Re: Best practices around "Page_PreRender" and "Page_Load" events

    Thanks ThunderMusic for the input.

    Hi Max,

    I think the "official" guidelines are scattered in following places:

    * ASP.NET page life cycle
    (http://msdn2.microsoft.com/en-us/library/ms178472.aspx)
    * Crash courses on creating controls
    (http://msdn2.microsoft.com/en-us/library/aa530687.aspx)

    Of course, the official documentation on creating controls is already the
    best place to look up information:

    #Creating Controls
    http://msdn2.microsoft.com/en-us/asp.net/aa336658.aspx


    Hope this helps.


    Regards,
    Walter Wang (wawang@online.microsoft.com, remove 'online.')
    Microsoft Online Community Support

    ==================================================
    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    ==================================================

    This posting is provided "AS IS" with no warranties, and confers no rights.


  8. Default Re: Best practices around "Page_PreRender" and "Page_Load" events

    Hi,
    for an ASP.NET Page cycle, we found this page to be REALLY useful when we
    developped our controls.
    http://weblogs.asp.net/jeff/archive/...04/172683.aspx

    I hope it helps

    ThunderMusic

    "Walter Wang [MSFT]" <wawang@online.microsoft.com> wrote in message
    news:1tx9Dhy0HHA.4844@TK2MSFTNGHUB02.phx.gbl...
    > Thanks ThunderMusic for the input.
    >
    > Hi Max,
    >
    > I think the "official" guidelines are scattered in following places:
    >
    > * ASP.NET page life cycle
    > (http://msdn2.microsoft.com/en-us/library/ms178472.aspx)
    > * Crash courses on creating controls
    > (http://msdn2.microsoft.com/en-us/library/aa530687.aspx)
    >
    > Of course, the official documentation on creating controls is already the
    > best place to look up information:
    >
    > #Creating Controls
    > http://msdn2.microsoft.com/en-us/asp.net/aa336658.aspx
    >
    >
    > Hope this helps.
    >
    >
    > Regards,
    > Walter Wang (wawang@online.microsoft.com, remove 'online.')
    > Microsoft Online Community Support
    >
    > ==================================================
    > When responding to posts, please "Reply to Group" via your newsreader so
    > that others may learn and benefit from your issue.
    > ==================================================
    >
    > This posting is provided "AS IS" with no warranties, and confers no
    > rights.
    >




+ Reply to Thread

Similar Threads

  1. email-display: "N", "D", " ": yeah; but "O"? How to MARK "O"?
    By Application Development in forum Mutt
    Replies: 0
    Last Post: 10-30-2007, 07:13 AM
  2. Replies: 3
    Last Post: 06-28-2007, 01:35 AM
  3. Replies: 0
    Last Post: 03-21-2007, 01:26 PM
  4. """""""""""""""""""""Visual C++ 2005 Express"""""""""""""""""
    By Application Development in forum DOTNET
    Replies: 0
    Last Post: 03-12-2006, 03:55 AM
  5. Tracing: "End ProcessPostData" and "Begin Page_Load"
    By Application Development in forum DOTNET
    Replies: 2
    Last Post: 10-06-2004, 02:17 AM