Philly .net tomorrow!

Surprise! I’ll be heading up to Philly tomorrow night for the Philly .net user group at our Malvern office. Sorry for the last-minute notice, but I just found out this morning.

Bill Wolff asked me if I’d do a little demo of ASP.NET “Atlas”, and I told him I’d be happy to oblige. The main presenter is MVP and ASPInsider, Jason Gaylord, speaking on Membership and Personalization in ASP.NET 2.0.

Should be a fun meeting. Hope to see you there!

Comments (2)

  1. Jerial says:

    I like your presentation of new features that can be easily plugged into the existing projects. I would like to know a little more of what is behind the screen on the server side.

    In particular, I am wondering during the call back,

    if a page object is created on the server side, and gets executed

    in the regular way. If yes, who gets in to trim the response stream to hold only the bits needed for the client. If not, who gets in to alter the regular process. I would really appreciate if you can tell me the name of the class, or point me to some links.

  2. gduthie says:


    The Atlas docs have the answer:

    "In typical ASP.NET 2.0 applications, when a postback occurs, the page is re-rendered. This causes the page to flash in the browser. On the server, during postback, the page lifecycle executes. This ultimately raises the control event that caused the postback and runs the event handler (for example, a Button control’s Click handler).

    "The ASP.NET "Atlas" UpdatePanel control eliminates the full page refresh. The UpdatePanel control is used to mark a region in the page that will be updated when a postback occurs, but without the traditional postback behavior in the client. On the server, the page still handles the postback and runs normally, such as raising event handlers. But during the final rendering of the page, only the regions defined by UpdatePanel controls are created. This is referred to as partial rendering."