Blazor Debug, Breakpoints not being hit. about dotnet-webapi-boilerplate HOT 6 OPEN

@kallievz I have added a small fix related to this. Can you please pull the latest from main branch and test this if your problem is solved?

from dotnet-webapi-boilerplate.

Hi @iammukeshm , is this for Blazor Debug, or the unauth exception?

from dotnet-webapi-boilerplate.

@kallievz it's for the Blazor Debug. I dont seem to have any Auth related issue.

from dotnet-webapi-boilerplate.

Hi @iammukeshm , running project now launch the browser, it hit the breakpoint once, and errors out with Unauth exception. Brower launches on different port as configured in appsetting.json, and seems to change everytime the project run. Using the one that start up from Aspire does not hit breakpoint. Is there a way to add Cors with only localhost instead of specifying port?
If it was just localhost, it would work, but now the port is set dynamically everytime project run,

from dotnet-webapi-boilerplate.

@kallievz so the blazor app is set to run on 7100 port. If this port is already in use, it would re-assign to a random port, which i think is happening in your case. Do check if the port is in use.

Else, as a work around, you can disable CORS.

Open up namespace FSH.Framework.Infrastructure.Cors.Extensions and edit the following, just add .AllowAnyOrigin()

internal static IServiceCollection AddCorsPolicy(this IServiceCollection services, IConfiguration config)
{
    var corsOptions = config.GetSection(nameof(CorsOptions)).Get<CorsOptions>();
    if (corsOptions == null) { return services; }
    return services.AddCors(opt =>
    opt.AddPolicy(CorsPolicy, policy =>
        policy.AllowAnyHeader()
            .AllowAnyMethod()
            .AllowAnyOrigin()));
}

from dotnet-webapi-boilerplate.

It could be a workaround, but would prefer to use Cors policy. A bit paranoid about unauthed access. I dont want to open that door, but for a dev environment i could prob do it.

It is being used already by Aspire Blazor app.
So it seems it is spinning up the Blazor app twice, and linking debugger to the new one not configured on port 7100, almost like 2 Blazor instances running, and one being linked.

from dotnet-webapi-boilerplate.