C# 3.0 Design Patterns: Use the Power of C# 3.0 to Solve Real-World ProblemsIf you want to speed up the development of your .NET applications, you're ready for C# design patterns -- elegant, accepted and proven ways to tackle common programming problems. This practical guide offers you a clear introduction to the classic object-oriented design patterns, and explains how to use the latest features of C# 3.0 to code them.
|
Contents
| 1 | |
| 8 | |
Composite and Flyweight | 49 |
Adapter and Façade | 74 |
Prototype Factory Method and Singleton | 101 |
Abstract Factory and Builder | 122 |
Strategy State and Template Method | 139 |
Chain of Responsibility and Command | 164 |
Common terms and phrases
Abstract Factory pattern Adapter pattern AddPhoto Album algorithm behavior blog Bridge pattern Builder pattern called Chain of Responsibility Client Clone Command pattern Composite pattern Console.WriteLine constructor Context context cover the lefthand create Decorator pattern delegate design patterns Element enumerator Façade pattern Factory Method Flyweight pattern foreach GetEnumerator handle handler IComponent Illustration To test implementation input instantiated interface Invoker ITarget Iterator pattern lefthand column Mediator pattern Memento pattern Method pattern MyOpenBook MySpaceBook namespace Node null object structure Observer pattern operations Output pattern example Pattern Players pattern theory code pattern UML diagram Photo Product Prototype pattern Proxy pattern public class public int public override string public static public string public void Request Seabird Seacraft Singleton pattern SpaceBook Specification Version 3.0 static void Main Strategy pattern string name Subject subsystems System.Collections.Generic Template Method theory code continued Visitor pattern yield return
Popular passages
Page 16 - Decorator using System; using System. Drawing; using System. Drawing. Drawing2D; using System. Windows. Forms; using System.
Page 24 - C# program consists of one or more compilation units, each contained in a separate source file. When a C# program is compiled, all of the compilation units are processed together. Thus, compilation units can depend on each other, possibly in a circular fashion.
Page 3 - Generics permit classes, structs, interfaces, delegates, and methods to be parameterized by the types of data they store and manipulate.
Page 24 - Namespaces C# programs are organized using namespaces. Namespaces are used both as an "internal" organization system for a program and as an "external" organization system — a way of presenting program elements that are exposed to other programs.
Page 4 - Partial types that allow classes, structs, and interfaces to be broken into multiple pieces stored in different source files for easier development and maintenance...