![]() Open the Startup.cs file and locate the call to UseDeveloperExceptionPage: public void Configure(IApplicationBuilder app, IWebHostEnvironment env) ![]() ![]() This is because of a piece of middleware part of ASP.NET Core named DeveloperExceptionPage. When working locally and errors happen, you get a much more detailed message in the browser. This is probably the fastest way to get some more details of the error happening. Not all of the actions may be applicable or even possible in your case. Here is a list of actions to run through, to help to figure out what went wrong. This page is sometimes referred to as the White Screen of Death, a spin on the Blue Screen of Death in Windows and the Yellow Screen of Death in ASP.NET. This means that something happened during the initialization of your app, why you won't even be able to launch any of your web pages. Everything works out on your machine and after deploying your site to the production environment, all you get is this error in the browser:Īs stated in the headline, the ASP.NET Core failed to startup. So, you spend days developing the next Facebook or Twitter in ASP.NET Core. In this article, I'll guide you through where to look and possible solutions to common startup problems. Problems during the startup of an ASP.NET Core project on your production environment can be extremely hard to debug.
0 Comments
Leave a Reply. |