Prism4.0ctp get started

Part 1.

Architects and developers need to spend some time and managers to fully understand and evaluate prism. You can evaluate the solution in the following four steps:

1. Fit Analysis ). Determine whether this guide meets your needs.

1. Initial Evaluation (preliminary evaluation ). Install, allow, and view the guide.

1. In-depth evaluation (deep evaluation ). Have a thorough understanding of this Guide.

1. Adoption (used ). Digest this guide and apply it to practice.

 

Details are as follows:

Step 1: Learn More

Prism is designed for complicated WPF/SilverlightProgramBorn. Prism can be considered in the following scenarios:

• You are building a composite program that displays information from multiple sources on the integrated user interface.

• You are developing, testing, and deploying mutually independent modules.

• More applications and views will be added to your application in the future.

• You need to quickly and securely change the application to meet the changing business needs.

• Your program is developed by multiple cooperative teams.

• Your program requires the implementation of WPF/Silverlight at the same time, and you want to share as much as possible between the two platformsCode.

If your program does not meet the requirements of the above scenarios, Prism may not be suitable for you. It may not be suitable for you: for example, your application consists of several simple interfaces, you are building a prototype or demo program, or your developers are not familiar with this idea and practice, and there is no time to learn it.

To determine whether or not prism is suitable for you, you need to understand the problems it is targeting as a solution. The following section will help you with an applicability analysis:

• When to use this guidance

• Goals and Benefits
• Modularity design concept
• Ui Composition Design Concept
• Intended audience

It takes 1-2 hours to understand these chapters.

 

Step 2: Preliminary Evaluation

To get a closer look at prism, you need to learn more about the design of the prism class library to determine how the composite application architecture adapts to your enterprise solution architecture. You also need to view the "helloworld" simple program code.

You need to know the following:

• Prism Library (PRISM Class Library)
• The following modes:
  • Separated presentation (displayed separately)
  • Dependency injection (dependency injection)

• Container design concept (container design concept)
• The following technical concepts:
  • Container and services)
  • Event aggregator)
  • Ui composition (ui composition)

Follow these steps to get started:

• Download and compile the prism Library
• Read WPF hands-on lab: getting started with the prism library or Silverlight hands-on lab: getting started with the prism Library

The preceding sections may take 3 to 4 hours.

 

Step 3: In-depth evaluation

A deep evaluation is required before the adoption of prism. It is recommended that you refer to Quick Start and stock trader reference implementation (stock trader RI) and then develop a concept verification program to gain an in-depth understanding of prism. You can also consider extending the class library or optimizing it as needed to meet your organizational needs.

Before implementing the concept verification program, you should first understand the following:

• Technical concept:
  • Bootstrapper (start loader)
  • Module)
  • Shell and view (appearance and view)
  • Commands (command)
  • Communication)
  • Multi-targeting)

• Quick Start Guide
• Familiar with stock trader reference implementation examples

Follow these steps to implement your verification program:

• Review the related how-to Chapter development activities.

• Refer to stock trader Ri to see how to implement characteristic tasks and functions.

• Review the deployment process. See deploying WPF applications with clickonce or deploying Silverlight applications.

• Review customization activities.

The time required for this step depends on the size and nature of your application.

 

Step 4: Use

Once prism is adopted, the goal is clear. Prism achieves the goal through the following channels:

• You can "need" and "do not need" prism class library section. For example, you can only use the required services.
• You can gradually add the prism class library function to an existing WPF/Silverlight English program.

• You can build a WPF/Silverlight application and share as much code as possible between the two platforms.

• Prism is non-intrusive and performs as follows:
  • Limits the traces of the prism class library in the code.
  • Limits the dependency on the properties of the custom prism class library. You can integrate existing class libraries and Prism class libraries by inheritance and combination (avoiding forcing you to inherit from classes in the prism class library ).

To use Prism, follow these steps:

• Learn how you will use the Class Library: directly adopt or customize to meet your needs.
• Refer to key decisions for decision making and communicate with other developers in the development team.
• Prism class library training. Developers need to know the following:
  • When to use this guidance
  • Prism assets
  • Technical Concept of UI composition UI Composition
  • Module technical concepts
  • Development activities Development Process
  • Sample Code of quickstarts and stock trader ri

• train designers to use Prism. Designers need to know the following:
  • when to use this guidance
  • UI design guidance overview