دانلود کتاب Building Enterprise Applications with Windows® Presentation Foundation and the Model View ViewModel Pattern

The Windows Presentation Framework (WPF), Silverlight. and Windows Phone 7 are the latest technologies for building flexible user interfaces (Ul) for applications built with Microsoft technology. All three rely on the XAML markup language to describe Ul elements and layout, and you can program applications for all three platforms with the most common of Microsoft .NET Framework languages: Visual Cn or Visual Basic .NET. If you are a .NET developer planning to create a new Line of Business (LOB) application using the .NET Framework, you should consider adopting one of these technologies as your Ul technology. At the same time, as you start planning to build an application based on one of these technologies, you should also seriously consider learning and applying the Model View ViewModel (MVVM) presentation pattern, a design pattern created specifically for these technologies.And that's what this book is about. You might be wondering, "Why another book on WPF?" Or, if you have already looked at the Table of Contents, you might be thinking, "Why another book about layering and design patterns?"To answer those questions, let me start by saying that over the years. I have noticed that what developers ask for the most is not the "Bible of patterns" or the "Bible of how to layer an applications instead, they want a simple, straightforward book that guides them through the development criteria for a real-world, yet simple, application that uses and explains patterns—but that is also reusable in future projects as a "template" for other applications.WPF and Silverlight are young technologies, and the percentage of developers moving to this new way of designing the Ul is still small. There are several reasons for this. First, the learning curve is relatively high. If you're used to Windows Forms, Java Swing, or Delphi, the way you design and structure an application using XAML and WPF is significantly different—in fact, I would call it "revolutionary."