This topic has not yet been rated - Rate this topic

Module Plug-in

Retired Content
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.

Problem

Your composite smart client application supports multiple back-end services. You want to assign different teams to independently develop the support for each service. Additionally, you do not want developers to modify existing code to incorporate new back-end services when they become available.

Solution

You can use the Composite UI Application Block to extend your applications with new modules. The Composite UI Application Block ModuleLoaderService uses the information in the profile catalog to determine which modules should be loaded at run time. It then loads the specified assemblies.

Assign different teams responsibility for different modules. When a new back-end service becomes available, create a new Composite UI Application Block module for the service. Deploy the assembly for the new module and an updated profile catalog.

Example

The reference implementations use modules. The following XML shows the profile catalog for the AppraiserWorkbench reference implementation.

<SolutionProfile xmlns="http://schemas.microsoft.com/pag/cab-profile" >
  <Modules>
    <ModuleInfo AssemblyFile="AppraiserWorkbenchModule.dll" />
  </Modules>
</SolutionProfile>

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)