asp.net core mvc displays empty page

Question

Please, I need help with a nagging issue with an asp.net core mvc app.

The app only shows blank home page - no contents at all including html markups. No controller is invoked even by typing url directly on the browser and no error is displayed.

I've created new app all over again a couple of times with the same result. Also, I've added statements below to the Configure method in the Startup class to no avail.

app.UseDefaultFiles();
app.UseStaticFiles();
app.UseIdentity();

Any guide to resolve this mystery would be highly appreciated.

Thanks.

 public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory) {
        loggerFactory.AddConsole(Configuration.GetSection("Logging"));
        loggerFactory.AddDebug();

        //add NLog to ASP.NET Core
        //loggerFactory.AddNLog();

        ////add NLog.Web
        //app.AddNLogWeb();

        //needed for non-NETSTANDARD platforms: configure nlog.config in your project root
        //env.ConfigureNLog("nlog.config");

        if (env.IsDevelopment()) {
            app.UseDeveloperExceptionPage();
            app.UseDatabaseErrorPage();
            app.UseBrowserLink();
        } else {
            app.UseExceptionHandler("/Home/Error");
        }

        app.UseDefaultFiles();
        app.UseStaticFiles();
        app.UseIdentity();

        // Add external authentication middleware below. To configure them please see http://go.microsoft.com/fwlink/?LinkID=532715
        app.UseMvcWithDefaultRoute();
        //app.UseMvc(routes => {
        //    routes.MapRoute(
        //        name: "default",
        //        template: "{controller=Home}/{action=Index}/{id?}");
        //});

        // For more details on creating database during deployment see http://go.microsoft.com/fwlink/?LinkID=615859
        try {
            using (var serviceScope = app.ApplicationServices.GetRequiredService<IServiceScopeFactory>()
                .CreateScope()) {
                serviceScope.ServiceProvider.GetService<ChurBaseContext>()
                     .Database.Migrate();

                var userManager = serviceScope.ServiceProvider.GetService<UserManager<ChurchMember>>();
                var roleManager = serviceScope.ServiceProvider.GetService<RoleManager<IdentityRole>>();

                serviceScope.ServiceProvider.GetService<ChurBaseContext>().EnsureSeedData(userManager, roleManager);
            }
        } catch { }
    }

jaybro · Accepted Answer · 2018-04-24 15:55:47Z

5

I had this behavior when I setup a Use() extension in the Startup.cs, above the UseMvc(), that did not invoke "await next();" at the end of the function.

app.Use(async (context, next) =>
{
    // some custom magic

    await next();// don't forget this
});

app.UseMvc(routes =>
{
    routes.MapRoute(
        name: "default",
        template: "{controller=Home}/{action=Index}/{id?}");
});

answered Apr 24, 2018 at 15:55

jaybro

1,5931 gold badge15 silver badges25 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

DotnetShadow · Accepted Answer · 2018-09-28 11:04:53Z

3

You can try adding, either:

app.UseStatusCodePages();

or

app.UseStatusCodePagesWithReExecute("/error/{0}");

For info on the latter you can see: [When using UseStatusCodePagesWithReExecute, statuscode is not sent to browser

answered Sep 28, 2018 at 11:04

DotnetShadow

7781 gold badge10 silver badges28 bronze badges

Comments

williamsandonz · Accepted Answer · 2016-12-16 01:30:15Z

0

app.UseMvcWithDefaultRoute(); //in startup.cs

or

app.UseMvc(routes =>
{
  routes.MapRoute(
    name: "default",
    template: "{controller}/{action}/{id?}",
    defaults: new { controller = "Home", action = "Index" });
});

answered Dec 16, 2016 at 1:30

williamsandonz

16.5k23 gold badges108 silver badges191 bronze badges

1 Comment

Joset Over a year ago

I have everything in place as mentioned but still experiencing the same issue. Not sure what I'm doing wrong, still. Thanks.

Sanket · Accepted Answer · 2016-12-16 06:46:39Z

0

This may happened because, you have not used MVC into execution pipeline.

In Configure method of startup class, you need to add like this-

public void Configure(IApplicationBuilder app, IHostingEnvironment env, ILoggerFactory loggerFactory)
        {
            ......

            app.UseStaticFiles();

            app.UseMvc(routes =>
            {
                routes.MapRoute(
                    name: "default",
                    template: "{controller=Home}/{action=Index}/{id?}");
            });
        }

or add UseMvcWithDefaultRoute like this-

app.UseMvcWithDefaultRoute();

This basically adds MVC to the IApplicationBuilder request execution pipeline.

See if this helps.

answered Dec 16, 2016 at 6:46

Sanket

20.2k10 gold badges74 silver badges84 bronze badges

6 Comments

Sanket Over a year ago

Also, check your browser console, you will see error like this- Failed to load resource: the server responded with a status of 404 (Not Found)

Joset Over a year ago

Thanks for the quick response. I've setup everything as instructed but no difference. No error in the browser console as well.

Sanket Over a year ago

Can you share complete configure method of startup?

Joset Over a year ago

I just did. Thanks.

Cheung Over a year ago

I have same issue. Everything works under Windows 10 with IISExpress, but not work on apache/centos.

|

George · Accepted Answer · 2020-02-16 20:39:31Z

0

When you see just a blank page and have no response other that the blank page, it can be caused by many things. These are two that I have seen:

A corrupt web.config
A web.config that is clashing with IIS. This could happen when a particular section is locked in your IIS configuration.

answered Feb 16, 2020 at 20:39

George

315 bronze badges

Collectives™ on Stack Overflow

asp.net core mvc displays empty page

5 Answers 5

Comments

Comments

1 Comment

6 Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

Comments

Comments

1 Comment

6 Comments

Comments

Linked

Related