Programming Books C Java PHP Python Learn more Browse Programming Books
Essential Windows Presentation Foundation (WPF) and over one million other books are available for Amazon Kindle. Learn more
  • List Price: $54.99
  • Save: $17.32 (31%)
Usually ships within 6 to 9 days.
Ships from and sold by
Gift-wrap available.
FREE Shipping on orders over $35.
Condition: Used: Good
Comment: 2007 Addison-Wesley Pub. softcover. Highlighting on 18 pages only. Lot of scuffing on page edges. Minor edge wear.
Access codes and supplements are not guaranteed with used items.
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Essential Windows Presentation Foundation (WPF) Paperback – April 21, 2007

ISBN-13: 978-0321374479 ISBN-10: 0321374479 Edition: 1st

Buy New
Price: $37.67
24 New from $31.00 36 Used from $0.01 1 Collectible from $9.98
Amazon Price New from Used from
"Please retry"
"Please retry"
$31.00 $0.01

Frequently Bought Together

Essential Windows Presentation Foundation (WPF) + Windows Presentation Foundation Unleashed (WPF) + Programming WPF
Price for all three: $116.88

Some of these items ship sooner than the others.

Buy the selected items together


Shop the New Digital Design Bookstore
Check out the Digital Design Bookstore, a new hub for photographers, art directors, illustrators, web developers, and other creative individuals to find highly rated and highly relevant career resources. Shop books on web development and graphic design, or check out blog posts by authors and thought-leaders in the design industry. Shop now

Product Details

  • Paperback: 512 pages
  • Publisher: Addison-Wesley Professional; 1 edition (April 21, 2007)
  • Language: English
  • ISBN-10: 0321374479
  • ISBN-13: 978-0321374479
  • Product Dimensions: 7 x 1.2 x 9.2 inches
  • Shipping Weight: 2.1 pounds (View shipping rates and policies)
  • Average Customer Review: 4.3 out of 5 stars  See all reviews (15 customer reviews)
  • Amazon Best Sellers Rank: #480,360 in Books (See Top 100 in Books)

Editorial Reviews

About the Author

Chris Anderson, architect in Microsoft’s Connected Systems Division, specializes in designing and architecting .NET technologies for the next generation of applications and services. In ten years at Microsoft, he has worked on technologies ranging from Visual Basic 6.0 and Visual J++ 6.0 to .NET Framework 1.0 and 1.1. In 2002, he joined the Windows Client team as an architect for Windows Presentation Foundation. Anderson has spoken at numerous conferences, including PDC, TechEd, WinDev, and DevCon.

Excerpt. © Reprinted by permission. All rights reserved.

Over the past nine years I have worked on many user interface (UI) projects at Microsoft. I have spent time working on Visual Basic 6.0, the version of Windows Foundation Classes that shipped with Visual J++ 6.0, Windows Forms for the .NET Framework, internal projects that never saw the light of day, and now, finally, Windows Presentation Foundation (WPF).

I started working on WPF about 18 months after the team was created, joining as an architect in the fall of 2002. At that time, and until late 2005, the team and technology were code-named Avalon. Early in 2003 I had the privilege of helping to redesign the platform, which we released as a technology preview for the Professional Developers Conference (PDC) 2003 in Los Angeles. WPF is the product of almost five years of work by more than 300 people. Some of the design ideas in WPF date back to products from as early as 1997 (Application Foundation Classes for Java was the beginning of some of the ideas for creating components in WPF).

When I joined the WPF team, it was still very much in research mode. The project contained many more ideas than could possibly ship in a single version. The primary goal of WPF—to replace all the existing infrastructure for building applications on the client with a new integrated platform that would combine the best of Win32 and the Web—was amazingly ambitious and blurred the lines between user interface, documents, and media. Over the years we have made painful cuts, added great features, and listened to a ton of feedback from customers, but we never lost sight of that vision.

A Brief History of GUI

Graphical user interfaces (GUIs) started in the early 1980s in the Xerox PARC laboratory. Since then, Microsoft, Apple, and many other companies have created many platforms for producing GUI applications. Microsoft’s GUI platform began with Windows 1.0 but didn’t gain widespread use until Windows 3.0 was released in 1990. The primary programming model for building GUI applications consisted of the two dynamic link libraries (DLLs): User and GDI. In 1991 Microsoft released Visual Basic 1.0, which was built on top of User and GDI, and offered a much simpler programming model.

Visual Basic’s UI model, internally called Ruby, 1 was far simpler to use than were the raw Windows APIs. This simplicity angered the developers who felt that programming should be difficult. The early versions of Visual Basic were significantly limited, however, so most developers building “real” applications chose to program directly to User and GDI. Over time, that changed. By the time the Microsoft world moved to 32-bit with the release of Windows 95 and Visual Basic 4.0, the VB crowd was gaining significant momentum and was offering a much wider breadth of platform features.

At about the same time there was another big shift in the market: the Internet. Microsoft had been working on a replacement for the Visual Basic UI model that was internally called Forms3. For various reasons, Microsoft decided to use this model as the basis for an offering in the browser space. The engine was renamed Trident internally, and today it ships in Windows as MSHTML.dll. Trident evolved over the years to be an HTML-specific engine with great text layout, markup, and scripting support.

Also around the same time, another phenomenon appeared on everyone’s radar: managed code. Visual Basic had been running in a managed environment for a long time (as had many other languages), but the introduction of Java by Sun Microsystems in 1994 marked the first time that many developers were exposed to the notion of a virtual machine. Over the next several years managed code became a larger and larger force in the market, and in 2002 Microsoft released its own general-purpose managed-code platform: the .NET Framework. Included in the .NET Framework was Windows Forms, a managed-code API for programming User32 and GDI+ (a successor to GDI32). Windows Forms was intended to replace the old Ruby forms package in Visual Basic.

As we entered the new millennium, Microsoft had four predominant UI platforms: User32/GDI32, Ruby, Trident, and Windows Forms. These technologies solve different sets of problems, have different programming models, and are used by different sets of customers. Graphics systems had also evolved: In 1995, Microsoft introduced DirectX, a graphics system that gave the programmer much deeper access to the hardware. But none of the four main UI technologies used this newfound power in a meaningful way.

There was a real problem to be solved here. Customers were demanding the richness of modern video games and television productions in their applications. Media, animation, and rich graphics should be everywhere. They wanted rich text support because almost every application displayed some type of text or documentation. They wanted rich widgets for creating applications, buttons, trees, lists, and text editors—all of which were needed to build the most basic application.

With these four major platforms a large percentage of the customers’ needs were met, but they were all islands. The ability to mix and match parts of the platforms was difficult and error-prone. From a purely selfish point of view, Microsoft management (well, I’ll name names: Bill Gates) was tired of paying four teams to build largely overlapping technologies.

In 2001, Microsoft formed a new team with a simple-sounding mission: to build a unified presentation platform that could eventually replace User32/GDI32, Ruby, Trident, and Windows Forms, while enabling the new scenarios that customers were demanding in the presentation space. The people who made up this team came largely from the existing presentation platform teams, and the goal was to produce a best-of-breed platform that could really be a quantum leap forward.

And so the Avalon team was formed. At PDC 2003, Microsoft announced Avalon (the code name at the time). Later the project was given the name Windows Presentation Foundation.

Principles of WPF

WPF has taken a long time to build, but for the entire life of this project, several guiding principles have remained constant.

Build a Platform for Rich Presentation

In descriptions of new technology, rich is probably one of the most overused words. However, I can’t think of a better term to convey the principle behind WPF. Our goal was to create a superset of features from all existing presentation technologies—from basic things like vector graphics, gradients, and bitmap effects, to more advanced things like 3D, animation, media, and typography. The other key part of the principle was the word platform. The goal was to create not merely a runtime player for rich content, but rather an application platform that people could use to build large-scale applications and even extend the platform to do new things that we never envisioned.

Build a Programmable Platform

Early on, the WPF team decided that both a markup (declarative) and code (imperative) programming model were needed for the platform. As we looked around at the time, it became clear that developers were embracing the new managed-code environments. Quickly, the principle of a programmable platform became a principle of a managed programming model. The goal was to make managed code the native programming model of the system, not a tacked-on layer.

Build a Declarative Platform

From the perspective of both customers and software developers, it seemed clear that the industry was moving to a more and more declarative programming model. We knew that for WPF to be successful, we needed a rich, consistent, and complete markup-based programming model. Again, a look at what was going on in the industry made it clear that XML was becoming the de facto standard for data interchange, so we decided to build an XML programming model, which became XAML (Extensible Application Markup Language).

Integrate UI, Documents, and Media

Probably the biggest problem facing customers who were building applications was the separation of pieces of functionality into isolated islands. There was one platform for building user interfaces, another for building a document, and a host of platforms for building media, depending on what the medium was (3D, 2D, video, animation, etc.). Before embarking on building a new presentation system, we set a hard-and-fast goal: The integration of UI, documents, and media would be the top priority for the entire team.

Incorporate the Best of the Web, and the Best of Windows

The goal here was to take the best features from the last 20 years of Windows development and the best features from the last 10 years of Web development and create a new platform. The Web offers a great simple markup model, deployment model, common frame for applications, and rich server connectivity. Windows offers a rich client model, simple programming model, control over the look and feel of an application, and rich networking services. The challenge was to blur the line between Web applications and Windows applications.

Integrate Developers and Designers

As applications become graphically richer and cater more to user experience, an entirely new community must be integrated into the development process. Media companies (print, online, television, etc.) have long known that a variety of designer roles need to be filled to create a great experience for customers, and now we are seeing that same requirement for software applications. Historically the tools that designers used were completely disconnected from the software construction process: Designers used tools like Adobe Photoshop or Adobe Illustrator to create rich designs, only to have developers balk when they tried to implement them. Creating a unified system that could natively support the features that designers required, and using a markup format (XAML) that would allow for seamless interop...

More About the Author

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

This book is great if you want to understand the why behind WPF.
T. Anderson
The book is good; I recommend it as a starting point or to complement other WPF learning resources.
This book is all about the philosophy behind the WPF design and architecture.
K. Osenkov

Most Helpful Customer Reviews

24 of 26 people found the following review helpful By Borek Bernard on September 5, 2007
Format: Paperback
Chris has always impressed me with his talent to explain even the hardest bits of WPF in an approachable fashion - I guess many Channel 9 and other dev-related sites visitors would agree with me. Therefore, I started reading Essential WPF with high expectations...

There is nothing wrong with the book itself, but the marketing is completely and utterly false. Chris himself emphasizes that he would like to talk about the "why-s" of the platform and this is the very reason why I bought his book - only to find out that nothing like that happens. Quite honestly, any technical author could write this book after reading Windows 3.0 SDK documentation thoroughly - there is very little added value or insight. There are moments when Chris writes "this may be confusing..." and in this very moment, you would expect "... but it was necessary because of this and that" but that almost never happens. You are left with doubts about the quality of WPF which is probably the worst thing an author can do.

Don't be confused as I was: this book is not about "why-s", it is not about reasoning, it is not about in-depth discussion of some decisions made. It is an extensive walkthrough through the WPF features, it is a description of the framework but nothing more. Of course you will find some insights in this book but they are definitely not in proportion to Chris's role in the WPF team and his otherwise great skills.

I, personally, started reading this book as a big fan of WPF and was left with doubts if all the complexity is really necessary (and some things are pretty complex compared to Flex which is my current development environment). Actually, I think that I enjoyed reading the WPF introductory articles in the Windows SDK 3.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
15 of 16 people found the following review helpful By Martin Hollingsworth on June 14, 2007
Format: Paperback
My intention is not to criticise this book but to provide a bit of balance to the other "superlative" filled reviews. I had already read Adam Nathan's book before this and had high expectations of this one after reading the other reviews. After finishing the book I can't really understand why the reviews were so glowing. There are definitely some design insights and Chapter 7 (Actions) covered the important Command pattern in good detail, but I'm struggling to think of any advantages over the WPF Unleashed book.

I would definitely recommend WPF unleashed over this and the bottom line is I'll be looking to sell my copy of Essential WPF as I don't see the value of having both.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
11 of 12 people found the following review helpful By T. Kirby Green on May 10, 2007
Format: Paperback
I thought no one could top Adam Nathan's WPF book, and this one doesn't top it - no what it does it match it but does so without tediously repeating the same material and approach. Chris Anderson's book is the one to read if you want to know the Why's and not just the What's - this is not just because Chris was one of the chief architects but because he explains it all so clearly. The book's organisation is wonderful, WPF has a huge surface area but Chris's presentation of it is effortless, enlightening and entertaining. I wouldn't hesitate to recommend this book.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
7 of 8 people found the following review helpful By EyelashViper on June 28, 2007
Format: Paperback
Overall, I was not impressed with this book. I kept getting the sense that I was about to learn something interesting when - poof! - the book moved on to another topic.

So, if you're looking for an introduction to the concepts of WPF, this might be for you but do not expect any in depth coverage of any topic. I was hoping for (consider the author's background) a lot more detail.

To put this review in perspective: I have been working with WPF for quite some time and have already been through other books on WPF (including Petzold's and Adam Nathan's - the later being my personal favorite to date).
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
4 of 4 people found the following review helpful By Corrado Cavalli on May 3, 2007
Format: Paperback
I bought all available WPF, so at the beginning i wondered: "What else can another book say new about WPF?". Well, this book has a lot of interesting details missing on others, probably because it has been written with an "inside" view, i knew a lot of architectural decisions reading it.

It has a good mix of xaml and code, it has pictures (!) and its a pleasant reading. Recommended to people migrating from Windows Forms to WPF world.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
4 of 5 people found the following review helpful By Ambrose on April 29, 2007
Format: Paperback
Essential Windows Presentation Foundation is precisely what the title says it is. What more can you ask for in a book? There are already several books on the RTM of WPF, and there are bound to be more. The unique value this one has is that it is written by Chris Anderson, who as most know, was an instrumental architect in designing WPF, and this (along with his direct connection to the others who worked on it) gives him insight that you just otherwise can't get.

In particular, I like that he often provides the thinking that went into particular design decisions. He readily admits in several places that the design of this or that was hotly debated, and one can only imagine that they would be. Having worked at a few commercial software vendors myself, I know how difficult it can be to know the best way to design a thing, and it can only be more challenging as your audience widens.

After this, the main thing that makes the book valuable is that it is deeply conceptual. The point of the book is not to be a reference, a recipie book, or a smattering of tutorials. Rather, the book provides, in a coherent form, the key principles underlying the different aspects of WPF. And by elaborating these principles, Chris establishes a strong sense that the Foundation was designed in a similarly coherent manner.

My favorite chapters were the one on Data, the one on Actions, and the Appendix. For a solutions architect and developer, these I think provide the most interesting meat. Of course, these types will likely want to delve into the first three chapters as well. In fact, the only one that I'd suggest you can probably get away with skipping is the one on Visuals; I found this one pretty dry and hard to push through.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Most Recent Customer Reviews

What Other Items Do Customers Buy After Viewing This Item?