5 Using EF Core in ASP.NET Core web applications

 

This chapter covers

  • Using EF Core in ASP.NET Core
  • Using dependency injection in ASP.NET Core
  • Accessing the database in ASP.NET Core MVC actions
  • Using EF Core migrations to update a database
  • Using async/await to improve scalability

In this chapter, you’ll pull everything together by using ASP.NET Core to build a real web application. Using ASP.NET Core brings in issues that are outside EF Core, such as dependency injection (covered in section 5.4) and async/await (covered in section 5.10). But they’re necessary if you’re going to use EF Core in this type of application.

This chapter assumes that you’ve read chapters 2-4 and know about querying and updating the database and what business logic is. This chapter is about where to place your database access code and how to call it in a real application. It also covers the specific issues of using EF Core in an ASP.NET Core (including Blazor Server) applications. For that reason, this chapter includes quite a bit about ASP.NET Core, but it’s all focused on using EF Core well in this type of application. I end with more general information on various ways to obtain an instance of the application’s DbContext for cases such as background tasks.

5.1 Introducing ASP.NET Core

5.2 Understanding the architecture of the Book App

5.3 Understanding dependency injection

5.3.1 Why you need to learn about DI in ASP.NET Core

5.3.2 A basic example of dependency injection in ASP.NET Core

5.3.3 The lifetime of a service created by DI

5.3.4 Special considerations for Blazor Server applications

5.4 Making the application’s DbContext available via DI

5.4.1 Providing information on the database’s location

5.4.2 Registering your application’s DbContext with the DI provider

5.4.3 Registering a DbContext Factory with the DI provider

5.5 Calling your database access code from ASP.NET Core

sitemap