How do you set the default document programmatically in the Program.cs file of an ASP.NET Core Web App (Razor Pages)

If I understand correctly, after deploying to IIS you get a 403.14 when trying to access the site on IIS. This sounds more like an IIS configuration or deployment issue. The Razor Pages end points service handles default end points like index.cshtml.

app.MapRazorPages();

Can you explain how the IIS application is configured and how the application was deployed?

using Microsoft.AspNetCore.Authentication;

using Microsoft.AspNetCore.Authentication.OpenIdConnect;

using Microsoft.AspNetCore.Authorization;

using Microsoft.AspNetCore.Hosting;

using Microsoft.AspNetCore.Mvc.Authorization;

using Microsoft.Identity.Web;

using Microsoft.Identity.Web.UI;

using Microsoft.Extensions.Hosting;

using Microsoft.AspNetCore.Builder;

using Microsoft.Extensions.FileProviders;

namespace SourceOfTruth2

{

public class Program

{

public static void Main(string[] args)

{

var builder = WebApplication.CreateBuilder(args);

// Add services to the container.

builder.Services.AddAuthentication(OpenIdConnectDefaults.AuthenticationScheme)

.AddMicrosoftIdentityWebApp(builder.Configuration.GetSection("AzureAd"));

builder.Services.AddAuthorization(options =>

{

// By default, all incoming requests will be authorized according to the default policy.

options.FallbackPolicy = options.DefaultPolicy;

});

builder.Services.AddRazorPages()

.AddMicrosoftIdentityUI();

var app = builder.Build();

// Configure the HTTP request pipeline.

if (!app.Environment.IsDevelopment())

{

app.UseExceptionHandler("/Error");

// The default HSTS value is 30 days. You may want to change this for production scenarios, see https://aka.ms/aspnetcore-hsts.

app.UseHsts();

}

app.UseHttpsRedirection();

app.UseStaticFiles();

app.UseRouting();

app.UseAuthentication();

app.UseAuthorization();

app.MapRazorPages();

app.MapControllers();

app.Run();

}

}

}

I'm guessing IIS is returning the 403.14 not the Razor Pages application. That's why I asked how the IIS application is configured and how the Razor Pages application was deployed. You did not explain either.

Try enabling directory browsing in IIS so you can at least see the files in the URL. Once you can see the files then you can probably figure out what's wrong.

My full comment didnt post for some reason...Yes it is IIS returning the 403 error. I had to manually move the application over to the web server since my companies security policies dont allow me to publish it through Visual Studio. I have since realized that my issue probably lies within my web.config file since the application did not automatically generate one for me. I think the config code is probably wrong, or the file is not in the correct location...or both.