You're reading from Enterprise Application Development with C# 9 and .NET 5 Enhance your C# and .NET skills by mastering the process of developing professional-grade web applications

Product type Paperback

Published in Mar 2021

Publisher Packt

ISBN-13 9781800209442

Length 610 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Application Development

Authors (5):

Ravindra Akella

Suneel Kumar Kunani

Bhupesh Guptha Muthiyalu

Arun Kumar Tamirisa

Rishabh Verma

+1 more

View More author details

Table of Contents (24) Chapters

Preface

1. Section 1: Architecting an Enterprise Application and its Fundamentals

2. Chapter 1: Designing and Architecting the Enterprise Application FREE CHAPTER

3. Chapter 2: Introducing .NET 5 Core and Standard

4. Chapter 3: Introducing C# 9

5. Section 2: Cross-Cutting Concerns

6. Chapter 4: Threading and Asynchronous Operations

7. Chapter 5: Dependency Injection in .NET

8. Chapter 6: Configuration in .NET Core

9. Chapter 7: Logging in .NET 5

10. Chapter 8: Understanding Caching

11. Section 3: Developing Your Enterprise Application

12. Chapter 9: Working with Data in .NET 5

13. Chapter 10: Creating an ASP.NET Core 5 Web API

14. Chapter 11: Creating an ASP.NET Core 5 Web Application

15. Section 4: Security

16. Chapter 12: Understanding Authentication

17. Chapter 13: Understanding Authorization

18. Section 5: Health Checks, Unit Testing, Deployment, and Diagnostics

19. Chapter 14: Health and Diagnostics

20. Chapter 15: Testing

21. Chapter 16: Deploying the Applications in Azure

22. Assessments

23. Other Books You May Enjoy

Understanding the CD pipeline

CD is a process by which you automate the deployment of code to target environments. CD pipelines use artifacts produced by CI pipelines and deploy to one or more environments. Like the CI pipeline, we can use YAML files or a classic editor to define a CD pipeline. You can specify conditions on the preceding stage execution state or add approval checks to deploy, which is a very common scenario for production deployments.

You can also configure to run automated UI tests to perform a sanity check post-deployment. Based on the sanity check results, you can configure to automatically promote code to a higher environment.

At any point in time, if the deployment to a stage fails, we can re-deploy code from previous releases. Depending on the configured retention policy under the project settings, Azure DevOps retains build artifacts so that it is easy to deploy code of any version at any time. If you find any issues with the application post-deployment...