No UseDatabaseErrorPage() extension method in Net Core 3.0

I have created Net Core 3.0 app and following code that worked in 2.2 now is not.


Looks like in 3.0 class DatabaseErrorPageExtensions does not exist within Microsoft.AspNetCore.Builder namespace. Am I missing some dependency? I have EntityFrameworkCore NuGet with Tools and Design added.


using Microsoft.AspNetCore.Builder;

not helped.

Add a reference to 'Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore', it appears that function is in that package now.

ASP.NET Core updates in .NET Core 3.0 Preview 4, NET Core 3.0 Preview 4 is now available and it includes a bunch of new updates to ASP. check out the improved Razor tooling and Blazor support in the C# extension. Configure method to move the route mapping logic into a call to Without any parameters, withAutomaticReconnect() will cause the  Breaking changes for migration from version 3.0 to 3.1. 11/25/2019; 7 minutes to read; In this article. If you're migrating from version 3.0 to version 3.1 of .NET Core, ASP.NET Core, or EF Core, the breaking changes listed in this article may affect your app.


Install-Package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore -Version 3.1.2

IApplicationBuilder does not contain UseDataBaseErrorPage , NET Core 3.1 and it looks like the UseDataBaseErrorPage method is not in the does not contain UseDataBaseErrorPage() method #16651. This version replaces the method name "InvokeAsync" by "SendAsync" on server side, but still uses "invoke" on client side. Although it's working, I think it's better if we can use the same name: "InvokeAsync" with "invoke" or "SendAsync" with "send".

[CLI] dotnet add package Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore --version 3.1.2


using Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore;

Add custom middleware in ASP.NET Core application, are software components that are assembled into an application pipeline to handle requests and responses. Each component chooses whether to pass the request on to the next component in the pipeline, and can perform certain actions before and after the next component is invoked in the pipeline. Using this version of ASP.NET Core 3.0.100-preview6-012264 App project builds and runs successfully xunit project that references project fails to build showing CS1061

ASP.NET Core - Middleware, What is middleware in ASP NET core and how important is it? How can we use classes like Screen in a .NET Core 3.0 WPF project? There are documentation pages for .NET Core 3.0 for them, so I assumed it should work. VS and the compiler tell me that the namespace Forms does not exist in System.Windows, so it feels like the classes are not in the 3.0 sdk.

What is Middleware in ASP.NET Core and How important is it?, UseStartup<Startup>() extension method because it points us to the settings where ASP NET Core Identity 3.0 are located. public class Program { Migrate from ASP.NET Core 2.2 to 3.0. 05/03/2020; 27 minutes to read +23; In this article. By Scott Addie and Rick Anderson. This article explains how to update an existing ASP.NET Core 2.2 project to ASP.NET Core 3.0.

What's new in ASP.NET Core 3.0, NET Core 3.0 as well as the changes to existing features. NET Core is now an SDK, not a set of discernable libraries. Instead of specifying MVC or Razor Pages as an extension of the IApplicationBuilder, you'll wire For the Configure method in Startup.cs , the separation exists there too. AddControllersWithViews‚Äč(). Stack Overflow for Teams is a private, secure spot for you and your coworkers to find and share information. Learn more IApplicationBuilder does not contain UseStaticFiles()

  • Tried reading msdn?……
  • Exactly, so this method should be but is not existing.
  • Worked like a charm
  • Thanks, it worked also in my side, the main reason for this error is that after upgrading to .net core 3.1, you should get rid of Microsoft.AspNetCore.App NuGet package which has many dependencies. Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore is one of the dependencies that we need to add individually in case we need them.
  • Worked for me thanks!
  • Works like charm! Thanks!
  • Your answer lacks clarity!