Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Architecting ASP.NET Core Applications - Third Edition

You're reading from  Architecting ASP.NET Core Applications - Third Edition

Product type Book
Published in Mar 2024
Publisher Packt
ISBN-13 9781805123385
Pages 806 pages
Edition 3rd Edition
Languages
Author (1):
Carl-Hugo Marcotte Carl-Hugo Marcotte
Profile icon Carl-Hugo Marcotte
Toc

Table of Contents (27) Chapters close

Preface 1. Section 1: Principles and Methodologies
2. Introduction 3. Automated Testing 4. Architectural Principles 5. REST APIs 6. Section 2: Designing with ASP.NET Core
7. Minimal APIs 8. Model-View-Controller 9. Strategy, Abstract Factory, and Singleton Design Patterns 10. Dependency Injection 11. Application Configuration and the Options Pattern 12. Logging Patterns 13. Section 3: Component Patterns
14. Structural Patterns 15. Behavioral Patterns 16. Operation Result Pattern 17. Section 4: Application Patterns 18. Layering and Clean Architecture 19. Object Mappers 20. Mediator and CQS Patterns 21. Getting Started with Vertical Slice Architecture 22. Request-EndPoint-Response (REPR) 23. Introduction to Microservices Architecture 24. Modular Monolith 25. Other Books You May Enjoy
26. Index

Learning the options interfaces

There are four main interfaces to use settings:

  • IOptionsMonitor<TOptions>
  • IOptionsFactory<TOptions>
  • IOptionsSnapshot<TOptions>
  • IOptions<TOptions>

We must inject one of those interfaces into a class to use the available settings. TOptions is the type that represents the settings that we want to access.

The framework returns an empty instance of your options class if you don’t configure it. We learn how to configure options properly in the next subsection; meanwhile, remember that using property initializers inside your options class can also be a great way to ensure certain defaults are used. You can also use constants to centralize those defaults somewhere in your codebase (making them easier to maintain). Proper configuration and validation are always preferred, but both combined can add a safety net.

Don’t use initializers or constants for default values that 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 €14.99/month. Cancel anytime