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

2. Introduction FREE CHAPTER

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

Understanding the Operation Result Design Pattern

This chapter explores the Operation Result pattern, starting simple and progressing to more complex cases. An operation result aims at communicating the success or the failure of an operation to its caller. It also allows that operation to return both a value and one or more messages to the caller.

Imagine any system in which you want to display user-friendly error messages, achieve some small speed gain, or even handle failure easily and explicitly. The Operation Result design pattern can help you achieve these goals. One way to use it is to handle the result of a remote operation, such as after querying a remote web service.

This pattern builds upon foundational object-oriented programming concepts. Having a whole chapter about it allows us to iterate and design different possibilities incrementally. Of course, the final design should always be based on your needs, so learning multiple options should help you make the right...