Quick overview of ASP.NET Ajax Ajax deep-dive Cover some key real-world problems Discuss solutions, patterns, opportunities Lots of demos And more of ASP.NET Ajax

Partial rendering Update a portion of the page without writing any script Ajax Control Toolkit Open source project at Lots of Ajax-enabled server controls Web services Exposing web services as JSON services Super simple access via script proxies and networking stack Script Framework (MicrosoftAjax.js) Type system, and general framework for creating Ajax apps

Ajax has become mainstream Users have come to expect it However, subtle use of Ajax is usually effective Don’t have to go overboard with flashy apps It is about creating better user experiences Fluid user interface matching user task flows Rich data visualization Intuitive data entry It is not just about updating page contents by issuing xmlhttp requests

Script complexity Indexability and SEO Navigation and bookmarkability Increasing user expectations Diagnostics/Tracing/MonitoringPerformanceAccessibility Browser API inconsistencies …

Increasing complexity with increased Ajax features Use appropriate framework features Script components, encapsulation of logic OOP Separation of content, presentation, and logic Partial rendering in ASP.NET Behaviors in ASP.NET Ajax Re-use and encapsulation mechanism Represent script logic that you attach to markup Usable in a variety of scenarios Enable better designer/developer workflow

Ajax updates don’t affect the browser history Breaks the back button Might also break bookmarkability It is an opportunity! You have a clean slate Add your own history points to create a better navigation model than regular post-backs ASP.NET Ajax History Feature Very simple API to abstract browser “nuances” Call addHistoryState() Handle the navigated event to detect state changes Updates URL fragment to also provide bookmarkability

Preserving indexability is a must for most sites Relies on presence of static data within pages Ajax apps often fetch data dynamically App structure and logic isn’t useful for searching An alternate Ajax pattern Embed data statically within the page Make every page of data independently discoverable via sitemaps Script consumes data and creates interactive presentation Script uses xmlhttp to implement paging as well

Search Engine View … … <img class=“photo” src=“…” <img class=“photo” src=“…” alt=“…” /> alt=“…” /> Search Engine View … … <img class=“photo” src=“…” <img class=“photo” src=“…” alt=“…” /> alt=“…” /> <script> document.write(‘ ’); </script> … … <script>document.write(‘</div>’);</script> <script> // Script to create map // Script to create map</script><script> document.write(‘ ’); </script> … … <script>document.write(‘</div>’);</script> <script> // Script to create map // Script to create map</script> Script-enabled Browser View … </div> <script> // Script to create map // Script to create map</script> Script-enabled Browser View … </div> <script> // Script to create map // Script to create map</script>

Increasing user expectations for functionality Ability to work with local files Expectations around faster applications Deeply integrating media experiences Using islands of Silverlight Can be used incrementally to light up existing Ajax apps Balancing reach and capabilities New capabilities to your application CLR-based execution, threads for background work Access to local storage and files Vector graphics, media

ASP.NET Ajax Docs, how-to videos, forums etc. Ajax Control Toolkit My Blog Slides + Samples My Contact Form

Prioritize creating better user experiences Think about where to apply Ajax in your applications Approach Ajax systematically Separate content and behavior Apply established patterns for addressing key Ajax challenges Leverage ASP.NET Ajax Solutions and framework for creating real-world Ajax apps

© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

Ajax apps have a lot more happening on the client Tracking script execution in production Handling errors internally and logging them End-user shouldn’t ever see script errors Other tracing and tracking scenarios

Broad discussion topic with several facets Script downloading/bandwidth consumption Script execution time Perception – get some rendering quick …ScriptManager.LoadScriptsBeforeUI One upcoming ASP.NET Feature: Script combining Reduces the number of script downloads per page