Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
An Atypical ASP.NET Core 6 Design Patterns Guide

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

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781803249841
Length 678 pages
Edition 2nd Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Carl-Hugo Marcotte Carl-Hugo Marcotte
Author Profile Icon Carl-Hugo Marcotte
Carl-Hugo Marcotte
Arrow right icon
View More author details
Toc

Table of Contents (31) Chapters Close

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

Object mapper

What is object mapping? In a nutshell, it is the action of copying the value of an object’s properties into the properties of another object. But sometimes, properties’ names do not match; an object hierarchy may need to be flattened and transformed. As we saw in the previous chapter, each layer can own its own model, which can be a good thing, but that comes at the price of copying objects from one layer to another. We can also share models between layers, but even then we need some sort of mapping at some point. Even if it’s just to map your models to Data Transfer Objects (DTOs) or view models, it is almost inevitable unless you are building a tiny application, but even then, you may want or need DTOs and view models.

Note

Remember that DTOs define your API’s contract. Having independent contract classes should help you maintain a system, making you choose when to modify them. If you skip that part, each time you change...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image