Microsoft Prism 4开发者指南：构建模块化MVVM应用

需积分: 9 36 浏览量更新于2024-07-30 收藏 9.2MB PDF 举报

《微软®Prism 4开发者指南》是2011年3月发布的一本技术文档，由Bob Brumfield、Geoff Cox、David Hill、Brian Noyes和Michael Puleio以及Karl Shiflett合作编撰。本书专注于Windows® Presentation Foundation (WPF) 和 Microsoft Silverlight®平台，指导开发者构建模块化的模型视图 ViewModel (MVVM) 应用程序。MVVM是一种软件设计模式，它提倡将应用程序的逻辑结构分解为三个主要部分：模型（Model）、视图（View）和ViewModel，通过这种方式实现松耦合和可测试性。书中内容包括但不限于以下要点： 1. **Prism 4介绍**：Prism 是一个开源框架，扩展了.NET Framework中的WPF和Silverlight应用，提供了构建复杂应用程序所需的架构和工具集。Prism强调组件化开发，使得应用程序易于维护、扩展和测试。 2. **模型视图视图模型（MVVM）**：核心理念是将应用程序的状态管理从视图层分离出来，通过ViewModel来处理业务逻辑和数据绑定。这样做的好处在于，视图仅关注用户界面，而ViewModel则负责与数据交互和业务规则，提高了代码的可重用性和独立性。 3. **模块化架构**：Prism鼓励开发者采用模块化设计，将应用程序划分为多个可独立部署和升级的部分，每个模块有自己的视图、ViewModel和数据模型，增强了系统的灵活性和可扩展性。 4. **Windows Presentation Foundation (WPF)**：作为底层技术，WPF提供了一套丰富的用户界面和图形工具，与Prism结合可以创建美观且功能强大的应用程序。开发者可以利用XAML语言和C#编写视图和ViewModel。 5. **Microsoft Silverlight**：在当时的版本中，Silverlight是一个流行的跨平台应用程序开发框架，适用于Web浏览器和嵌入式设备。Prism为Silverlight开发者提供了一致的开发体验和架构支持。 6. **MEF (Managed Extensibility Framework)**：该指南可能包含了如何使用MEF来实现框架和服务的插件化，使应用程序能够动态加载和卸载扩展功能，提升系统的可扩展性。 7. **示例和实践**：书中包含了许多实战案例和示例代码，帮助读者理解和掌握Prism的使用方法，以及如何在实际项目中应用MVVM架构。 8. **版权和使用声明**：此文档仅为开发者提供参考，信息和观点可能会随时间变化，使用时需自行承担风险。书中某些例子是虚构的，没有与任何真实产品或服务相关联。《微软®Prism 4开发者指南》是一份实用的资源，适合想要提升WPF和Silverlight应用程序开发技能，尤其是希望通过MVVM架构构建模块化、可维护应用的开发者。阅读这本书将有助于理解Prism框架的核心原理和实践技巧，从而更好地利用这些技术构建高效、现代的软件解决方案。

What comes after “Hello, World?”

WPF and Silverlight developers are blessed with an abundance of excellent books,

videos, and online articles from which to learn how to build a single screen application.

These resources teach data binding, dependency properties, resources, styles, effects,

control templating, and many other fundamentals of XAML platform programming.

There’s no lack of tutorials on Model-View-ViewModel (MVVM), the justly popular and

predominant pattern for structuring an individual screen. But they stop short of the guid-

ance you need to deliver a non-trivial application in full.

Your ﬁrst screen goes well. You add a second screen and a third. Because you started

your solution with the built-in “Navigation Application Template,” adding new screens

feels like hanging shirts on a closet rod. You are on a roll. Until the harsh reality of real

application requirements sets in.

As it happens, your application has 30 screens not three. There’s no room on that

closet rod for 30 screens. Some screens are modal pop-ups; you don’t navigate to a pop-

up. Screens become interdependent such that user activity in one screen triggers changes

that propagate throughout the UI. Some screens are optional; others are visible only to

authorized users. Some screens are permanent, while other screens can be opened and

closed at will. You discover that navigating back to a previously displayed screen creates

a new instance. That’s not what you expected and, to your horror, the prior instance is

gone along with the user’s unsaved changes.

You realize that the out-of-the-box navigation is useless to you. You are resigned to

ripping it out and starting over. You consider building your own UI framework, but decide

to survey the scene ﬁrst. Surely someone has been down this road before. Surely someone

has published guidance and code to cope with the scale, variety, and complexity of your

real world application.

Someone has. The Microsoft Prism Library, code samples, and the book that you’re

reading now are the culmination of a ﬁve year quest to consolidate the best advice and

techniques from experts and practitioners in the ﬁeld.

Prism covers all of the scenarios just mentioned and many more. You’ll ﬁnd guidance

and supporting code for:

•

Partitioning the application into modules, those semi-autonomous islands of

functionality that should be developed and maintained independently.

Foreword

xvi

•

Mechanisms for loading modules asynchronously or on-demand so that applications

start quickly.

•

A publish/subscribe apparatus, the event aggregator, for passing messages among

components that cannot and should not connect directly.

•

Dynamically composing a complex screen, such as a dashboard, from several simpler

views.

•

Creating pages using View-First, ViewModel-First, or a controller that makes them

and coordinates them.

•

Initializing views with parameters or context information as when launching an

editor that targets a selected customer.

•

Guidelines and examples of automated tests for views and view models that

depend upon asynchronous data sources.

Many developers will see in Prism an all-in-one solution from a single trusted source.

They have neither the time nor inclination to scrutinize each component, compare it with

competitors, and assemble a custom framework from a buffet of alternatives. They fear

the “Franken-framework” of mismatched parts from multiple vendors. For this audience,

Prism is a safe and reliable choice. I don’t know of a solution as comprehensive, well

documented, or well supported. The design is sound. The code is solid and tested. Great

applications are built exclusively with Prism and yours can be one of them.

Other developers look at Prism a little differently. They see Prism as a compendium

of patterns and strategies for building WPF and Silverlight UIs. The shipped software is a

confederation of optional components. They might embrace Prism modularity but prefer

someone else’s alternative to DelegateCommands. They could choose a third party injec-

tion container instead of MEF or Unity. They might use a region only in the shell or not

use regions at all. For this audience, Prism is a source of inspiration and advice. It’s a

storehouse of code to use, ignore, or replace as they see ﬁt.

One of Prism’s great and hard won achievements is that it supports both perspectives

equally. It’s a coherent framework of cooperating components that work seamlessly to-

gether. Yet each part stands on its own, ready to collaborate, without depending on any

of the others.

Whether you adopt it whole or in part, I urge you to read this book, study the Quick-

Starts, and explore the reference implementations. That’s the best way to master Prism

itself. Better still, you’ll become a more capable programmer, equipped to anticipate real-

world UI architectural challenges and solve them effectively.

Ward Bell

VP Technology, IdeaBlade (www.ideablade.com)

Silverlight MVP

Do w n loa d fro m Wo w ! eB o o k < w ww. w o web o o k.c o m>

xvii

Foreword

Building WPF and Silverlight applications can be challenging, especially for those new to

the technology. Building clean, maintainable, extensible, testable, loosely coupled ones—

with no idea where to start—is close to impossible. In late 2007, I was privileged to get a

call from Glenn Block at Microsoft asking if I was interested in working with the Micro-

soft patterns & practices team on a project that would become the ﬁrst release of Prism,

which was released as the Composite Application Guidance for WPF in June 2008.

I had been working with WPF on complex customer applications, trying to ﬁgure out

the best practices and patterns on my own. This was a fantastic opportunity to provide

some guidance and feedback to the team on what mattered, what worked, and what

didn’t, in real customer apps that I had worked on. I had worked with various patterns &

practices teams before as an external advisor, but this was my ﬁrst opportunity to come

in as a consultant and participate as an integral part of the team.

It turned out to be a wonderful experience for me. The team included some of the

most intelligent, creative, and fun individuals I have had a chance to work with in this in-

dustry. The maturity of the team’s development process, the effort that they put into

collecting community input and keeping the community involved throughout the devel-

opment process, and their collective design and coding prowess and professionalism

made it clear from the start that the right people were working on guiding the .NET de-

velopment community on the right way to build apps. I learned a ton in the process and

hopefully contributed something that helped make Prism a better product. So, naturally

I was delighted when I got the chance to work closely with the team again on the release

of Prism 4.

Prism 4 offers many things to many people. One of the biggest misconceptions is that

because it offers so much, it is too big or too complicated for smaller apps. One of the

early design goals of Prism was to keep the concerns of Prism separated in the same way

Prism helps you separate your own application’s concerns in the presentation layer. I think

the team did a great job of doing that, and you can easily use just commands, or just

events, or just modularity, or just UI composition or some combination of the above in

ways that are minimally intrusive to the rest of your application code. Add to that the new

Model-View-ViewModel (MVVM) pattern guidance, Managed Extensibility Framework

(MEF) integration, and navigation functionality of Prism 4, and you have a great set of

tools in a toolkit that can help you develop apps of any size.

xviii

If you are writing a small app, there are some great tools and techniques in here that

will help you to keep your app from becoming a maintenance liability. If you are develop-

ing a large application with a complex UI, you need something like Prism 4 to keep you

from being overwhelmed by the complexity and the volume of code that can result from

not basing your app on well-deﬁned design patterns and thoroughly tested code to help

you implement those patterns.

This book is another new feature of Prism 4. Previous releases provided great docu-

mentation in a standard Help format, consisting of many short topics with links to related

topics. And while that format is essential when you are writing code and need to look up

little bits and pieces to keep you moving forward, there was a very important phase of

just getting up to speed on Prism and learning the concepts that was being neglected. You

couldn’t read a book, end-to-end, or chapter by chapter to learn the concepts and see

some code to make those concepts clear, because no such book existed (much as I tried

to ﬁnd the time to write that book myself).

The structure of a good book on a programming technology is inherently different

from good help topics. This book is structured so that you can read it from cover to

cover or just refer to the topics that interest you, without having to be at your computer

as you do so. To supplement the book, the help documentation online has additional

material, including hands-on labs and advanced information about the reference imple-

mentations and QuickStarts. Because the book is available in print and e-book form, you

can take it with you on a plane or to the beach, so that when you do sit down to write

your Prism code, you are immediately productive and past the “What is it and how do I

use it” phase. You can then refer to the online help, hands-on labs, QuickStart topics, and

so on when you are at your computer and using Visual Studio.

Additionally, with this book you get the collective knowledge of the entire team, not

just the perspective of a single or small group of authors. All of the Prism developers and

designers collaborated and contributed to the content you will ﬁnd in this book. If one

person wrote a portion, several others reviewed, commented, and improved it. However,

you are primarily getting the content from the developers who wrote the features, which

is a rare opportunity. Customers often ask me: “Where is the best place to start learning

about Prism, and how can I use it?” In the past, I had to point them to a fragmented

collection of articles, podcasts, and blog posts. Now I have a simple and easy answer, and

I can point them one place – right here to this book.

Brian Noyes

Chief Architect, IDesign Inc. (www.idesign.net)

Silverlight MVP

Introduction1

Prism provides guidance designed to help you more easily design and build rich, ﬂexible,

and easy-to-maintain Windows Presentation Foundation (WPF) desktop applications,

Rich Internet Applications (RIAs) built with the Microsoft

Silverlight

browser plug-in,

and Windows Phone 7 applications. Prism uses design patterns that embody important

architectural design principles, such as separation of concerns and loose coupling. These

patterns help you to design and build applications by using loosely coupled components

that can evolve independently but that can be easily and seamlessly integrated into the

overall application. These types of applications are known as composite applications.

Note: Prism was the code name for the guidance formally known as the Composite

Application Guidance for WPF and Silverlight. For brevity and conciseness, and due to

customer demand, this guidance is now referred to simply as Prism.

Prism is intended for software developers who are building WPF or Silverlight appli-

cations that typically feature multiple screens, rich user interaction, and data visualization,

and that embody signiﬁcant presentation and business logic. These applications typically

interact with multiple back-end systems and services and, using a layered architecture,

may be physically deployed across multiple tiers. It is expected that the applications will

evolve signiﬁcantly over their lifetimes in response to new requirements and business

opportunities. In short, these applications are built to last and built for change. Applica-

tions that do not demand these characteristics may not beneﬁt from using Prism.

Prism includes reference implementations, QuickStarts, reusable library code (the

Prism Library), and extensive documentation. This version of Prism targets the Microsoft

.NET Framework version 4 and Silverlight version 4, and includes new guidance related to

the Model-View-ViewModel (MVVM) pattern, navigation, and the Managed Extensibility

Framework (MEF). Because Prism is built on the .NET Framework 4 (which includes WPF)

and Silverlight 4, familiarity with these technologies is useful for evaluating and adopting

Prism.

It should be noted that, while Prism is not difﬁcult to learn, developers must be ready

and willing to embrace patterns and practices that may be new to them. Management

understanding and commitment is crucial, and the project deadline must accommodate

an investment of time up front for learning these patterns and practices.

剩余279页未读，继续阅读

sasa007

粉丝: 7
资源: 6

Microsoft Prism 4开发者指南：构建模块化MVVM应用

yarn : 尤法加载文件 C: Users 12200 AppData Roaming npm yarn.ps1， 因为在此系统上察止运行脚本。 自天住细信息， 诸荟兑 https :/go .mi rosoft.com/fwlink/?LinkID=135170 中的 about Execution Policies. 所在位置 行:1 字符:1 +15.8k

解决Windows 11安装安卓子系统，发布的框架“Microsoft.UI.Xaml.2.6”错误，亲测成功。

新编Visual Basic 6.0教程.part2

新编Visual Basic 6.0教程.part1

家具仓库条码管理系统解决方案.pdf

Microsoft Chart Controls for .NET Framework支持各种丰富的图表选项

软考论文范例解读：信息系统项目管理与设计方法的应用

Markdown 是一种轻量级标记语言，它允许人们使用易读易写的纯文本格式编写文档 .zip

Go语言简易指令树实现.zip

基于java的新生报到系统的开题报告.docx

最新资源

yarn : 尤法加载文件 C: Users 12200 AppData Roaming npm yarn.ps1，因为在此系统上察止运行脚本。自天住细信息，诸荟兑 https :/go .mi rosoft.com/fwlink/?LinkID=135170 中的 about Execution Policies. 所在位置行:1 字符:1 +15.8k