Lab1 comments

commentaries from codeplex Hands on Labs documents:

Note: The required application block assemblies are signed and included with the Web Client Software Factory. The software factory installer installs them to the Microsoft Practices Library folder and records the location in a registry key (see HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\patterns and practices\Web Client Factory\MicrosoftPracticesLibraryBinaryPath). By default, the Create Web Client Solution recipe uses this location to search for the required assemblies.

• Foundational modules. A foundational module exposes functionality that is shared across the application and does not contain Web pages. For example, a foundational module can contain code that provides instrumentation, such as logging.
•          Business modules. A business module encapsulates a set of concerns of your application and contains Web pages. Typically, business modules are independent from one another and do not expose functionality to other modules.

Typical components of a business module are a combination of related Web pages, page flows, business logic, and services. The following are examples of business modules:

• A module that contains a specific application feature area, such as reports
• A module that contains use cases around a specific back-end system, such as loan processing

By default, solutions created with the Web Client Solution template include a Web site with a business module named Shell. This module is associated with the root folder of the Web site. This means that all pages in the root Web site folder belong to the Shell module.

After you run the Add Business Module recipe, you will have the following elements in your solution:

·         A C# class library project. This is the module class library. It contains a default view interface with a presenter, an empty folder named Services, a module initialization class, and a module controller. You will store services, view interfaces, presenters, and controllers in this project.

·         A folder in the Web site that has a default view implementation and a Web.config file. The Composite Web Application Block uses the module information in the Web.config file to load the module when the application starts. You will store view implementations in this folder.

·         A test project for the module. This project includes unit tests for the module initialization class and the presenter class of the default view. It also includes a mock module controller you can use to test your presenters.

 

• http://www.codeplex.com/websf/Release/ProjectReleases.aspx?ReleaseId=6897