Book Image

Hands-On Design Patterns with C# and .NET Core

By : Gaurav Aroraa, Jeffrey Chilberto
Book Image

Hands-On Design Patterns with C# and .NET Core

By: Gaurav Aroraa, Jeffrey Chilberto

Overview of this book

Design patterns are essentially reusable solutions to common programming problems. When used correctly, they meet crucial software requirements with ease and reduce costs. This book will uncover effective ways to use design patterns and demonstrate their implementation with executable code specific to both C# and .NET Core. Hands-On Design Patterns with C# and .NET Core begins with an overview of object-oriented programming (OOP) and SOLID principles. It provides an in-depth explanation of the Gang of Four (GoF) design patterns, including creational, structural, and behavioral. The book then takes you through functional, reactive, and concurrent patterns, helping you write better code with streams, threads, and coroutines. Toward the end of the book, you’ll learn about the latest trends in architecture, exploring design patterns for microservices, serverless, and cloud native applications. You’ll even understand the considerations that need to be taken into account when choosing between different architectures such as microservices and MVC. By the end of the book, you will be able to write efficient and clear code and be comfortable working on scalable and maintainable projects of any size.
Table of Contents (19 chapters)
Free Chapter
1
Section 1: Essentials of Design Patterns in C# and .NET Core
4
Section 2: Deep Dive into Utilities and Patterns in .NET Core
10
Section 3: Functional Programming, Reactive Programming, and Coding for the Cloud

Encapsulation

Encapsulation is another fundamental concept in OOP where the details of a class, that is, the attributes and methods, can be visible or not visible outside the object. With encapsulation, a developer is providing guidance on how a class should be used as well as helping to prevent a class from being handled incorrectly. For example, let's say we wanted to only allow adding PetAnimal objects by using the AddPet(PetAnimal) method. We would do this by having the PetOwner class's AddPet(PetAnimal) method available while having the Pets attribute restricted to anything outside the PetAnimal class. In C#, this is possible by making the Pets attribute private. One reason for doing this would be if additional logic was required whenever a PetAnimal class was added, such as logging or validating that the PetOwner class could have a pet.

C# supports different levels...