You're reading from An Atypical ASP.NET Core 6 Design Patterns Guide A SOLID adventure into architectural principles and design patterns using .NET 6 and C# 10

Product type Paperback

Published in Mar 2022

Publisher Packt

ISBN-13 9781803249841

Length 678 pages

Edition 2nd Edition

Languages

Tools

.NET

Concepts

Design Patterns

Author (1):

Carl-Hugo Marcotte

View More author details

Table of Contents (31) Chapters

Preface

1. Section 1: Principles and Methodologies FREE CHAPTER

2. Introduction

3. Automated Testing

4. Architectural Principles

5. Section 2: Designing for ASP.NET Core

6. The MVC Pattern Using Razor

7. The MVC Pattern for Web APIs

8. Understanding the Strategy, Abstract Factory, and Singleton Design Patterns

9. Deep Dive into Dependency Injection

10. Options and Logging Patterns

11. Section 3: Designing at Component Scale

12. Structural Patterns

13. Behavioral Patterns

14. Understanding the Operation Result Design Pattern

15. Section 4: Designing at Application Scale

16. Understanding Layering

17. Getting Started with Object Mappers

18. Mediator and CQRS Design Patterns

19. Getting Started with Vertical Slice Architecture

20. Introduction to Microservices Architecture

21. Section 5: Designing the Client Side

22. ASP.NET Core User Interfaces

23. A Brief Look into Blazor

24. Assessment Answers

25. Acronyms Lexicon

26. Other Books You May Enjoy

27. Index

Appendices

1. Appendix A

2. Appendix B

The Operation Result pattern

The Operation Result design pattern can be very simple to more complex. In this section, we explore multiple ways to use that pattern. We start with its simplest form and build on that until we can return messages, values, and add severity levels as the result of an operation.

Goal

The role of the Operation Result pattern is to give an operation (a method) the possibility to return a complex result (an object), which allows the consumer to:

[Mandatory] Access the success indicator of the operation (that is, whether the operation succeeded or not).
[Optional] Access the result of the operation if there is one (the return value of the method).
[Optional] Access the cause of the failure if the operation was not successful (error messages).
[Optional] Access other information that documents the operation’s result. This could be as simple as a list of messages or as complex as multiple properties.

This can...