Book Image

ASP.NET Core 5 for Beginners

By : Andreas Helland, Vincent Maverick Durano, Jeffrey Chilberto, Ed Price
Book Image

ASP.NET Core 5 for Beginners

By: Andreas Helland, Vincent Maverick Durano, Jeffrey Chilberto, Ed Price

Overview of this book

ASP.NET Core 5 for Beginners is a comprehensive introduction for those who are new to the framework. This condensed guide takes a practical and engaging approach to cover everything that you need to know to start using ASP.NET Core for building cloud-ready, modern web applications. The book starts with a brief introduction to the ASP.NET Core framework and highlights the new features in its latest release, ASP.NET Core 5. It then covers the improvements in cross-platform support, the view engines that will help you to understand web development, and the new frontend technologies available with Blazor for building interactive web UIs. As you advance, you’ll learn the fundamentals of the different frameworks and capabilities that ship with ASP.NET Core. You'll also get to grips with securing web apps with identity implementation, unit testing, and the latest in containers and cloud-native to deploy them to AWS and Microsoft Azure. Throughout the book, you’ll find clear and concise code samples that illustrate each concept along with the strategies and techniques that will help to develop scalable and robust web apps. By the end of this book, you’ll have learned how to leverage ASP.NET Core 5 to build and deploy dynamic websites and services in a variety of real-world scenarios.
Table of Contents (19 chapters)
Section 1 – Crawling
Section 2 – Walking
Section 3 – Running

Chapter 3 – Dependency Injection

  1. There are four types of dependency injections (DIs): constructor, method, property, and view injections. The constructor injection is the most commonly used approach for building ASP.NET Core applications.
  2. There are three types of DI lifetimes: transient, scoped, and singleton.

    Use a transient lifetime when you are unsure about how you should register the service. This is the safest option to use, and it's probably the most commonly used because services are created each time they are requested. This lifetime works best for lightweight and stateless services because they are disposed at the end of the request. Be aware, though, that a transient lifetime can potentially impact the performance of your application, especially if you are working on a huge monolith application, where the dependency reference is massive and complex.

    Use a scoped lifetime when you want an object to be created once per client web request. This is to ensure...