TechEd Braindump: ASP.Net 2.0:Advanced Server Controls with WebParts

 Speaker: Andres Sanabria

 

  • This guy just opened the IDE and didn’t resize his font size. I hate this! How am I supposed to follow along when all I see is red, blue and black blurs?
  • Composite Controls combines the functionality of one or more existing controls
  • The associated designer ensures child controls are created at design time as well.
  • Script OM: New Features
    • DefaultButton
    • Maintain scroll position on Postback
    • Focus, SetFocusOnError (for validation)
    • Web Resources
    • Out-of-band callbacks
  • Script OM: Generate and render client-script
    • Valid XHTML <script> tags
    • Provides API to register inline script or reference a *.js file
  • Controls con override to delegate focus to a child control if they want explicit control.
  • Web Resources: Simple deployment model of client files.
    • Package scripts, images, style sheets, etc. as assembly resources.
    • Instead of installing into “aspnet_client” folder
  • Script Callbacks
    • Page is interactive while the server process request
    • No browser flashing or loss of scroll position
    • Does not add to the navigation history
    • Modeled after post-back event handling
    • Implements a script callback function
    • Page framework handles partial page execution.
  • Script Callbacks sound really cool. Is this their answer to AJAX?
  • Asynchronous Task
    • Allows a container to register an asynchronous task to the page.
    • Container will be notified when task competed, time-out or ended.
    • Time out is defined at the page directive
    • Control developers can alter the rendering based on the async task result.
  • Control State
    • The essential bits of information to allow controls to ensure expected behavior
    • Separated out of view state. Page developer can turn off view state without losing functionality. Control state cannot be turned off.
    • Controls must opt-in to participate in this mechanism. Should store only the essentials, so control state doesn’t become another view state. Properties stored in control state should not be saved in view state as well.
  • He talks about how to integrates Web Parts in your controls. Check on this…
  • The demos are useless. Not because they don’t do anything but because I can’t see the code.
  • I’ve got to go. No I really it mean I’ve got to go! Too much bottled water lying around.

Disclaimer: These are my notes from my experience at TechEd 2005. I do not guarantee the validity or accuracy of these notes. They are my thoughts and what information I felt was important at the time.