Guidance provided by Responsive Composite Web Client Reference Implementation

As I was creating the home page for the new Reference Implementation that we just shipped, I realized that we demonstrate how to solve a number of technical challenges . I want to highlight these to give you an idea of the richness of our most current OrderManagement Reference Implementation. 

The reference implementation demonstrates how to solve the following technical challenges:

  • Composability : Building a composite web application
    • Modularity: Building complex sites based on modules that can be independently developed, tested, versioned, and deployed
    • Page composition: Creating composite Web pages that contain multiple user control views. The user controls can be used across modules and can be independently developed, tested, versioned, and deployed.
    • Testing of UI Logic: Utilizing unit tests to test Web page logic
  • Responsiveness : Improving usability and performance of the composite user interface utilizing ASP.NET AJAX.
    • Autocomplete : Providing a list of suggestions to a user that are retrieved based on the characters they have entered.
    • Validation : Validating user input on both the Web browser and the Web server. 
    • Live Form: Dynamically updating a field in the browser based on input from another field.
    • Live Search : Searching against LOB data from within the browser. 
    • Live Grid : Adding, Removing and Modifying records in a grid.
    • Popup : Utilizing AJAX popup's to dynamically display data that is retrieved from the server.
    • JSON Service: Calling a Web service from the browser.
  • UI Appearance: Creating and modifying the look and feel of the UI
    • Layout management: Creating a common user experience across different independent modules, separating the responsibility of the UI design from UI development.
    • User profile–based UIs: Changing the behavior of the UI based on the user identity and profile information
    • Navigation: Providing role-based site navigation.
  • Security : Improving site security
    • Authentication: Identifying registered users of a site
    • Authorization: Changing permissions for different users
    • Data security: Validating input data to reduce the probability of cross-site scripting and SQL injection attacks. 
  • Manageability:
    • Easy deployment: deploying and updating modules independently of other modules.
    • Logging and Exception Management: Providing a standard logging and exception management approach to ensure the operations team can more easily operate the application.

If you see a challenge that you have, you can step through a running example that demonstrates application-specific code built on reusable guidance. You can also copy sections of the source code that implements any particular guidance into your own applications.

Additionally, the documentation that shipped with the Reference Implementation provides information as to how these technical challenges were implemented. This is a new approach for our Reference Implementation documentation. I would like to hear if this provides you with the information you need to solve these technical challenges.

So go download the reference implementation and let me know what you think.