Book Image

Software Architecture with C# 9 and .NET 5 - Second Edition

By : Gabriel Baptista, Francesco Abbruzzese
Book Image

Software Architecture with C# 9 and .NET 5 - Second Edition

By: Gabriel Baptista, Francesco Abbruzzese

Overview of this book

Software architecture is the practice of implementing structures and systems that streamline the software development process and improve the quality of an app. This fully revised and expanded second edition, featuring the latest features of .NET 5 and C# 9, enables you to acquire the key skills, knowledge, and best practices required to become an effective software architect. This second edition features additional explanation of the principles of Software architecture, including new chapters on Azure Service Fabric, Kubernetes, and Blazor. It also includes more discussion on security, microservices, and DevOps, including GitHub deployments for the software development cycle. You will begin by understanding how to transform user requirements into architectural needs and exploring the differences between functional and non-functional requirements. Next, you will explore how to carefully choose a cloud solution for your infrastructure, along with the factors that will help you manage your app in a cloud-based environment. Finally, you will discover software design patterns and various software approaches that will allow you to solve common problems faced during development. By the end of this book, you will be able to build and deliver highly scalable enterprise-ready apps that meet your organization’s business requirements.
Table of Contents (26 chapters)
24
Another Book You May Enjoy
25
Index

Blazor forms and validation

Similar to all major SPA frameworks, Blazor also offers specific tools for processing user input while providing valid feedback to the user with error messages and immediate visual clues. The whole toolset is known as Blazor Forms and consists of a form component called EditForm, various input components, a data annotation validator, a validation error summary, and validation error labels.

EditForm takes care of orchestrating the state of all input components, through an instance of the EditContext class that is cascaded inside of the form. The orchestration comes from the interaction of both input components and the data annotation validator with this EditContext instance. A validation summary and error message labels don't take part in the orchestration but register to some EditContext events to be informed about errors.

EditForm must be passed the object whose properties must be rendered in its Model parameter. It is worth pointing out that...