Responsive Composite Web Client Reference Implementation

Cannot resolve release macro, invalid id.
Click here to see the documentation

What's the value of this guidance?

The reference implementation is an executable sample Order Entry application that demonstrates integrating the Web Client Guidance in to create a responsive composite solution. The implementation of the reference implementation follows the same project structure generated by the Automation Guidance Bundle. You can use the reference implementation in different ways. You 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.

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 Page Views that contain multiple User Control Views. The User Controls can be used across modules and can be independently developed, tested, versioned, and deployed.
    • Dependency Injection: Providing application classes external dependencies in a declarative fashion,
  • 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 the server as it is entered from within the browser. Reusing object validation across screens, applications and layers.
    • 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. Utilizing Server Side paging and sorting to improve performance.
    • Live Grid : Adding, Removing and Modifying records in a grid.
    • Popup : Utilizing AJAX popups to dynamically display data that is retrieved from the server.
    • JSON Service: Calling a Web service from the browser.
  • UI Appearance :
    • Layout management: Creating a common user experience across different independent modules, separating the responsibility of the UI design
    • 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: Protecting user and site information from unauthorized access
  • Misc :
    • Easy deployment: Minimizing the complexity to deploy new or updated functionality to a site
    • System availability and scaling: Maximizing uptime and minimizing the time to diagnose problems
    • Functional Testing Utilizing unit tests to test Web page logic
    • Mock respository: Utilizing a mock repository to test an applicaiton without requiring a database dependency

You can use the reference implementation in different ways. You 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.

What is the concept?

The Responsive Web Client Reference Implementation is a executable Order Entry sample application. Within the application you can create, delete and retrieive orders as well as search for existing customers.
Order Details.jpg
The application demonstrates the features that you may find useful in applications. To do this, it implements solutions for common, and recurrent, challenges that developers face when creating responsive line-of-business Web applications. It is not meant for completeness; instead, it selectively implements solutions to different challenges (many features of a real corporate order entry system are not implemented).

The reference implementation uses the blocks from the Composite Web Client Library and Enterprise Library.

What are some scenarios to consider using this guidance for?

  • Building a composite Order Entry application.
  • Creating an Order Page View that contains an Order Entry User Control View.
  • Popup customer search screen that returns the selected customer to a control.
  • Updating the Order Item Total based on the quantity entered.
  • Popup to preview an Order dynamically from within a results grid.
  • Providing suggestions on the client for City based on the selected State.
  • Providing suggestions on the client for Zip based on the selected City and State.
  • Validating an Order from the client without requiring a full postback.
  • Providing Role based Navigation for an Order Management site.

Who should use this library?

This library is for Developers and Architects who are interested in developing composite Line-Of-Business ASP.NET Web applications.

What is in the Reference Implementation?

The Reference Implementation Guidance Bundle contains the following elements:
  • Application Block Assemblies: Contains the assemblies for the Composite Web Application Block, ObjectBuilder which is required by the Composite Web Application Block, the ContextSensitiveAutoCompleteExtender control, the ServerSideValidationExtender control, and the ObjectContainerDataSource control.
  • Order Management Source Code: The source code for the OrderManagement reference implementation.
  • Documentation: Documentation explaining how the OrderManagement reference implementation solves a set of technical challenges.

What needs to be installed?

.NET Framework 3.5 Bundle

.NET Framework 2.0 Bundle

Installation

.NET Framework 3.5 Bundle

  1. Install all prerequisites for the bundle.
  2. Execute the bundle installer.
  3. Read and accept the EULA.
  4. Specify the destination folder.
  5. Copy the AjaxControlToolkit.dll assembly to %bundle destination folder%\Lib\AjaxControlToolkit3.5.
Optional for functional testing:
  • Copy the WatiN binaries to %bundle destination folder%\Lib\WatiN.

.NET Framework 2.0 Bundle

  1. Install all of the prerequisites for the bundle.
  2. Execute the bundle installer.
  3. Read and accept the EULA.
  4. Specify the destination folder.
  5. Copy the AjaxControlToolkit.dll assembly to %bundle destination folder%\Lib\AjaxControlToolkit.
Optional for functional testing:
  • Copy the WatiN binaries to %bundle destination folder%\Lib\WatiN.

Known issues

Click here to for this list of known issues

Last edited Jun 17, 2008 at 9:18 PM by jonathan, version 18

Comments

No comments yet.