Book Image

An Atypical ASP.NET Core 5 Design Patterns Guide

By : Carl-Hugo Marcotte
Book Image

An Atypical ASP.NET Core 5 Design Patterns Guide

By: Carl-Hugo Marcotte

Overview of this book

Design patterns are a set of solutions to many of the common problems occurring in software development. Knowledge of these design patterns helps developers and professionals to craft software solutions of any scale. ASP.NET Core 5 Design Patterns starts by exploring basic design patterns, architectural principles, dependency injection, and other ASP.NET Core mechanisms. You’ll explore the component scale as you discover patterns oriented toward small chunks of the software, and then move to application-scale patterns and techniques to understand higher-level patterns and how to structure the application as a whole. The book covers a range of significant GoF (Gangs of Four) design patterns such as strategy, singleton, decorator, facade, and composite. The chapters are organized based on scale and topics, allowing you to start small and build on a strong base, the same way that you would develop a program. With the help of use cases, the book will show you how to combine design patterns to display alternate usage and help you feel comfortable working with a variety of design patterns. Finally, you’ll advance to the client side to connect the dots and make ASP.NET Core a viable full-stack alternative. By the end of the book, you’ll be able to mix and match design patterns and have learned how to think about architecture and how it works.
Table of Contents (27 chapters)
1
Section 1: Principles and Methodologies
5
Section 2: Designing for ASP.NET Core
11
Section 3: Designing at Component Scale
15
Section 4: Designing at Application Scale
21
Section 5: Designing the Client Side
25
Acronyms Lexicon

Testing made easy through ASP.NET Core

The ASP.NET Core team made our life easier by designing ASP.NET Core for testability; most of the testing is way easier than before the ASP.NET Core era. Internally, they use xUnit to test .NET Core and EF Core, and we use xUnit as well throughout the book. xUnit is my favorite testing framework; what a nice coincidence. We are not going full-TDD-mode for all samples as it would deviate our focus from the matter at stake, but I did my best to bring as much automated testing as possible to the table! Why? Because testability is usually the sign of a good design, which allows me to prove some concepts by using tests instead of words.

Moreover, in many code samples, the test cases are the consumers, making the program lighter without building a full user interface over it. That allows us to focus on the patterns that we are exploring instead of getting our focus scattered over some boilerplate code.

How do you create an xUnit test project...