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

by Gaurav Aroraa, Jeffrey Chilberto (Coauthor)

Design Patterns, essentially are reusable solutions to common programming problems. When used correctly, they address crucial software requirements with ease and reduced costs. This book will uncover effective ways to use design patterns specific to both C# and .NET Core 2.0. The book will also demonstrate the implementation of these patterns through executable code.

The book begins with an overview of Object Oriented Programming and SOLID principles. You will learn about the importance of design patterns in C# and .NET Core and how the Gang of Four patterns can be used in an application. The book will build an application while showing the implementation of Builder, Decorator, Factory, Visitor, and Strategy patterns. You will learn about patterns used for concurrent programming in .NET Core. You will also learn about functional and reactive programming in C# and .NET Core. The book will take you through design patterns for modern architectures like microservices, serverless and cloud native.

By the end of the book, you will be able to efficiently address common problems faced while developing applications and be comfortable working on scalable and maintainable projects of any size.

410 pages, Paperback

Published July 1, 2019

Reviews

[Александр · Rating 3 out of 5]

Книга - разочарование.
Столько всего анонсировано, но по факту рассказано далеко не все и совсем не подробно.

[Miles Ramage · Rating 3 out of 5]

This book has done a fantastic job of introducing me to new and *crucial* information on my software development journey. This book has helped me to fully grasp the importance of implementing design patterns in my code that--up until finding this book--I barely even knew existed.

That being said, the case studies used in the book do an *atrocious* job of informing the reader of the accompanying changes that are being made behind the scenes--particularly in the chapters regarding ASP.NET Core and later.

Many times the author didn't include the contents of classes, folders, or methods as they were being added: I would be following along with an exercise and all of a sudden the author would make a method call or reference an entire class that the book *never* included a definition for. Sure, I could pull up the accompanying online code to access what I was missing, but the book never explicitly stated that I *needed to* when this happened. This approach frequently left me wondering if I'd missed something, so I was left constantly backtracking before confirming that the content was indeed missing from the book.

After struggling through Chapter 6 *twice* in this fashion, I eventually put the book down for good. Although the book starts out incredibly strong, I cannot recommend it in good conscience.