Jagamisviis:

Development Activities

  • Artikkel
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.

Figure 1 illustrates the mapping of composite application concepts to How-to topics included with the Composite Application Guidance.

Ff921120.dad548fc-7782-4918-bda3-402e0f9810cf(en-us,PandP.10).png

Figure 1
Mapping of composite application concepts to How-to topics

The next sections describe activities that developers usually perform when creating applications based on the Composite Application Library. Each How-to topic listed in the following sections provides the main steps for performing a particular task. As you review the How-to topics, consider how they can be applied to your application.

Note

This guidance includes a HelloWorld solution you can use to try the procedures in the How-to topics. To open the HelloWorld solution, run the file Open Hello World Solution.bat.

Creating Your Solution

A solution based on the Composite Application Library is a solution that you can use as a starting point for your composite Windows Presentation Foundation (WPF) application. The solution includes recommended practices and techniques and is the basis for the procedures in the Composite Application Guidance for WPF. For procedures related to creating a solution that uses the Composite Application Library, see How to: Create a Solution Using the Composite Application Library.

Bootstrapper

The bootstrapper is responsible for the initialization of an application built using the Composite Application Library. Having a bootstrapper gives you more control of how the Composite Application Library components are wired up to your application. The following topics contain procedures that customize the bootstrapper class:

For more information about the bootstrapper, see the Bootstrapper technical concept.

Modules

A module encapsulates a set of related concerns. Modules are independently developed and deployed, and they interact with each other to create an application. For procedures related to creating modules, see the following topics:

For more information about modules, see the Module technical concept.

Regions

Conceptually, a region is a mechanism that developers can use to expose to the application's Windows Presentation Foundation container controls—those that permit child elements—as components that encapsulate a particular visual way of displaying views (typically, views are user controls). Regions can be accessed in a decoupled way by their name and support adding or removing views dynamically at run time. For procedures related to regions, see the following topics:

For more information about the regions, see the Region technical concept.

Views

Views are objects that contain visual content. For more information about views, see the following topics:

For more information about the shell and views, see the Shell and View technical concept.

Services

A service is an object that provides functionality in a loosely coupled way to other components. These components can be in the same module or in other modules. The Composite Application Library includes a set of basic services that you can use in your applications. You can also develop your own services to provide infrastructure capabilities that are specific to your applications. For procedures related to services, see the following topic:

  • How to: Register and Use Services. This topic describes how to register and obtain references to services in an application that uses the Composite Application Library and the Unity container.

For more information about the services, see the Container and Services technical concept. For more information about when to use shared services, see the Communication technical concept.

Commands

Commands are a way to handle user interface (UI) actions. They are a loosely coupled way to bind the UI to the logic that performs the action. For procedures related to commands, see the following topics:

For more information about the commands, see the Commands technical concept. For more information about when to use commands, see the Communication technical concept.

Events

The Composite Application Library provides an event mechanism that enables communications between loosely coupled components in the application. By using this mechanism, based on the event aggregator service, publishers and subscribers can communicate through events that do not have a direct reference to each other. For more information about events, see the following topics:

For more information about events, see the Event Aggregator technical concept. For more information about when to use events, see the Communication technical concept.

Deploy

By using ClickOnce deployment, you can publish Windows-based applications to a Web server or network file share for simplified installation. The Composite Application Guidance for WPF includes guidance that helps you use ClickOnce to deploy an application built using the Composite Application Library. For more information, see the following topics:

For more information about ClickOnce Deployment, see Deploying WPF Applications with ClickOnce.

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.