Programming .NET 3.5

Chapter 8. Implementing Design Patterns with .NET 3.5

Though you may not realize it, you are actually holding two books in your hand. (Don't panic, you only have to pay for one!) They exist in the same space, at the same time; not side by side but in the same words, the same pages, and the same illustrations; separated not by chapters, headings, or content, but only by perspective.

One book is a programmer's guide to a set of new technologies. The second book describes how .NET 3.5 can be viewed as an integrated set of technologies that facilitates the key architectural patterns we've all been trying to implement for the past decade.

You don't have to accept the latter premise to read this book, but it may give you some new options. In the long run, incorporating these architectural patterns into your programming may be as revolutionary as the move from procedural to object-oriented programming.

Tip

Here is the primary theory behind this book, in a nutshell: you can approach .NET 3.5 as a set of new, individual technologies for presentation, communication, and workflow that includes dramatic client-side performance enhancements for web development; additionally, you can approach .NET 3.5 as an integrated framework designed to help you move beyond object-oriented programming and step up to object-oriented design based on high-level industry-standard architectural patterns.

These perspectives are not mutually exclusive; you can (and we hope you will) move between them. However, you may ...