1. Scelta della tecnologia di presentazione dei dati

2. Windows User Interfaces “Full-blown” Windows Forms applications Great control over the user experience Must be deployed to users Forms with embedded HTML Greater runtime flexibility Script security concerns Additional code required to “hook” HTML to form Application plug-ins Implement your UI in an existing host application (for example, Microsoft Office)

3. Browser-based User Interfaces Implement a custom error page and global exception handler ASP.NET client-side validation uses JavaScript, so provide server-side validation in controller functions as well Expose only the required methods and properties of custom controls Use ViewState, Session, and Application appropriately Use user process components to transition between pages Implement controller functions separately

4. Mobile Device User Interfaces Take the form factor into account Design for smaller screen Minimize data input Web-based mobile devices Pocket PC, WAP. iMode, etc. Use Mobile Internet Toolkit Smart Devices Pocket PC (.NET Compact Framework) Tablet PC (pen and ink API)

5. Document-based User Interfaces Working from the “outside” Gathering data: User fills in document and submits it for processing; the application parses the document to extract the data Reporting data: The application uses automation to generate a document containing the required data Working from the “inside” Gathering data: The user enters data in a predefined template and macros in the host application are used to call your business components Reporting data: Custom menus, buttons, and smart tags can be used to retrieve application data and display it

6. Richness vs. Complexity - Microsoft Presentation Technologies UX Richness Developer Productivity ASP.NET ASP.NET 2.0 (HTML) Windows Forms 2.0 Win32 Direct 3D v9 Availability: 20052006 DHTML 1997 ASP.NET “Atlas” Approachable Direct 3D v10 Richness Windows Presentation Foundation Optimized Richness & Approachable Ajax

7. Demo

8. Summary – Why Microsoft? Most widely used tools and runtime Most comprehensive application platform Significantly more productive than Oracle, IBM and SAP J2EE environments Standards-based for open interoperability Scalable, reliable and secure Significantly lower license costs than commercial J2EE application servers

9. © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.