Real-World Implementation of C# Design Patterns: Overcome daily programming challenges using elements of reusable object-oriented software

Cover
Title Page
Copyright and Credits
Foreword
Contributors
Table of Contents
Preface
Part 1: Introduction to Patterns (Pasta) and Antipatterns (Antipasta)
Chapter 1: There\'s a Big Ball of Mud on Your Plate of Spaghetti
	Technical requirements
	No battle plan survives first contact with the enemy
		The Stovepipe system
	The Big Ball of Mud
		Time
		Cost
		Experience
		Skill
		Visibility
		Complexity
		Change
		Scale
	The Golden Hammer
	A throwaway code example
	How can patterns help?
	Summary
	Questions
	Further reading
Chapter 2: Prepping for Practical Real-World Applications of Patterns in C#
	Becoming a prepper
	Technical requirements
	Spaghetti < lasagna < ravioli – software evolution explained with pasta
		Spaghetti code
		Lasagna code
		Ravioli – the ultimate in pasta code
	The foundational principle – writing clean code
		You should write code that is readable by humans
		Establishing and enforcing style and consistency
		Limiting cognitive load
		Terse is worse
		Comment but don’t go overboard
	Creating maintainable systems using SOLID principles
		The Single Responsibility principle
		The Open-Closed Principle
		The Liskov Substitution principle
		The Interface Segregation principle
		The Dependency Inversion principle
	Measuring quality beyond the development organization
		Code reviews
		Overall design
		Functionality
	Summary
	Further reading
Part 2: Patterns You Need in the Real World
Chapter 3: Getting Creative with Creational Patterns
	Technical requirements
	The following story is fictitious
	The initial design
	No pattern implementation
	The Simple Factory pattern
	The Factory Method pattern
	The Abstract Factory pattern
	The Builder pattern
	The Object Pool pattern
	The Singleton pattern
	Summary
	Questions
	Further reading
Chapter 4: Fortify Your Code With Structural Patterns
	Technical requirements
	B2B (back to bicycles)
	The Decorator pattern
	The Façade pattern
	The Composite pattern
	The Bridge pattern
	Summary
	Questions
	Further reading
Chapter 5: Wrangling Problem Code by Applying Behavioral Patterns
	Technical requirements
	Meanwhile, back at the bicycle factory
	The Command pattern
		Applying the Command pattern
		Coding the Command pattern
		Testing the Command pattern’s code
	The Iterator pattern
		Applying the Iterator pattern
		Coding the Iterator pattern
		Trying out the new iterator
	The Observer pattern
		Applying the Observer pattern
		Coding the Observer pattern
	The Strategy pattern
		Applying the Strategy pattern
		Coding the Strategy pattern
	Summary
	Questions
Part 3: Designing New Projects Using Patterns
Chapter 6: Step Away from the IDE! Designing with Patterns Before You Code
	Technical requirements
	A bad day at the agency
	Bumble Bikes factory – Dallas, Texas
	A physical rehabilitation clinic – Dallas, Texas
	Designing with patterns
	The first pass
		The seat
		The frame
		Wheels and casters
		The motor for the powered chair
		The steering mechanism for the powered chair
		The battery for the powered chair
		The track drive system for the Texas Tank
	Adding patterns
	The first design meeting
	The second pass
	The Builder pattern
	The Singleton pattern
	The Composite pattern
	The Bridge pattern
	The Command pattern
	Summary
	Questions
	Further reading
Chapter 7: Nothing Left but the Typing – Implementing the Wheelchair Project
	The crack of noon
	Setting up the project
		Wheelchair components
		Finishing the wheelchair base classes
	Finishing up the composite
	Implementing the Builder pattern
		Another refactor
		Adding concrete component classes
		Wrapping up the Builder pattern
	Adding the Singleton pattern
	Painting the chairs with the Bridge pattern
	Summary
	Questions
	Further reading
Chapter 8: Now You Know Some Patterns, What Next?
	Patterns we didn’t discuss
		Prototype
		Adapter
		Flyweight
		Chain of Responsibility
		Proxy
		Interpreter
		Mediator
		Memento
		State
		Template Method
		Visitor
	Patterns beyond the realm of OOP
		Software architecture patterns
		Data access patterns
	Creating your own patterns
		Name and classification
		The problem description
		The solution description
		Consequences of using the pattern
	Not everybody likes patterns
	Summary
	Sundance Square – Fort Worth, Texas
	Further reading
Appendix 1: A Brief Review of OOP Principles in C#
	Technical requirements
	A quick background of C#
		C# is a general-purpose language
		C# is purely and fully object-oriented
		C# uses a static, strong type system
		C# has automatic bounds checking and detection for uninitialized variables
		C# supports automated garbage collection
		C# code is highly portable
	Language mechanics in C#
		Variables in C#
		Classes
	Encapsulation
		C# auto-implemented properties
		Accessor logic with backing variables
	Inheritance
	Interfaces
		Defining interfaces
		Implementing interfaces
	IDEs for C# development
		Visual Studio
		VS Code
		Rider
	Summary
	Further reading
Appendix 2: A Primer on the Unified Modeling Language (UML)
	Technical requirements
	The structure of a class diagram
		Classes
		Interfaces
		Enumerations
		Packages
	Connectors
		Inheritance
		Interface realization
		Composition
		Association
		Aggregation
		Directed association
		Dependency
	Notes
	Best practices
		Less is more – don’t try to put everything in one big diagram
		Don’t cross the lines
		The most direct path for lines leads to a mess
		Parents go above children
		Keep your diagrams neat
	Summary
	Further reading
Index
Other Books You May Enjoy