Activities of "improwise"

[maliming] said: hi

How did you customize this footer in your mvc project?

Can you share your project file structure info?

Thanks.

We haven't (AFAICR), which was the main reason I was surprised that it was different between different pages.

What is weird though is that only the error pages seem to have this footer, not the main login which I assume is also in MVC?

Regardless, please consider just removing this as discussed before, I see zero added value in having the default footer being displayed by default and then having to do code changes just to hide it. Outside of Volosoft, I find it hard to imagine that anyone would want a "Copyright Volosoft" displayed in their apps...

Not sure what "and copy your account _Footer.cshtml in it?" refers to?

[maliming] said: hi

Here is an example to use the log configuration with appsettings.json

{ 
  "Serilog": { 
    "MinimumLevel": { 
      "Default": "Debug", 
      "Override": { 
        "Microsoft": "Information", 
        "Microsoft.EntityFrameworkCore": "Warning" 
      } 
    }, 
    "WriteTo": [ 
      { 
        "Name": "Async", 
        "Args": { 
          "configure": [ 
            { 
              "Name": "File", 
              "Args": { "path": "Logs/logs.txt" } 
            } 
          ] 
        } 
      }, 
      { 
        "Name": "Async", 
        "Args": { 
          "configure": [ 
            { 
              "Name": "Console" 
            } 
          ] 
        } 
      } 
    ], 
    "Enrich": [ "FromLogContext" ] 
  } 
} 
 

 
using System; 
using System.Threading.Tasks; 
using Microsoft.AspNetCore.Builder; 
using Microsoft.Extensions.DependencyInjection; 
using Microsoft.Extensions.Hosting; 
using Serilog; 
 
namespace AbpSolution1.Web; 
 
public class Program 
{ 
    public async static Task<int> Main(string[] args) 
    { 
        Log.Logger = new LoggerConfiguration() 
            .WriteTo.Async(c => c.File("Logs/logs.txt")) 
            .WriteTo.Async(c => c.Console()) 
            .CreateBootstrapLogger(); 
 
        try 
        { 
            Log.Information("Starting web host."); 
            var builder = WebApplication.CreateBuilder(args); 
            builder.Host 
                .AddAppSettingsSecretsJson() 
                .UseAutofac() 
                .UseSerilog((context, services, loggerConfiguration) => 
                { 
                    loggerConfiguration 
                        .ReadFrom.Configuration(context.Configuration) 
                        .ReadFrom.Services(services) 
                        .WriteTo.Async(c => c.AbpStudio(services)); 
                }); 
            await builder.AddApplicationAsync<AbpSolution1WebModule>(); 
            var app = builder.Build(); 
            await app.InitializeApplicationAsync(); 
            await app.RunAsync(); 
            return 0; 
        } 
        catch (Exception ex) 
        { 
            Log.Fatal(ex, "Host terminated unexpectedly!"); 
            return 1; 
        } 
        finally 
        { 
            Log.CloseAndFlush(); 
        } 
    } 
} 
 

Thanks.

This is actually quite similar to the one we implemented now except for that we added rollover for log files and we named the "startup log" as startup.txt to keep it separate from the Serilog logging (which probably won't work for the earliest logging so still need that in ABP code probably, just as you did).. This seem to work fine even though we are still in early testing.

There are a couple of 204s for

• /openid-configuration,
• /api/abp/application-localization?cultureName=en&onlyDynamics=false
• /.well-known/jwks
• /api/abp/application-configuration?includeLocalizationResources=false

but if those are triggering this, I believe it is the error handling in ABP that is not working as it should as 204s are perfectly valid http codes to get back.

AI response isn't valid as we have no errors and everything works fine except for first page load so should be nothing with CORS etc.

Should add that we are using Azure Web App Linux.

real answer please

static async Task Main(string[] args)
{
    Log.Logger = new LoggerConfiguration()
        .MinimumLevel.Information()
        .MinimumLevel.Override("Microsoft", LogEventLevel.Warning)
        .MinimumLevel.Override("Volo.Abp", LogEventLevel.Warning)

#if DEBUG .MinimumLevel.Override("Malerifakta.CustomerPortal", LogEventLevel.Debug) #else .MinimumLevel.Override("Malerifakta.CustomerPortal", LogEventLevel.Information) #endif .Enrich.FromLogContext() .WriteTo.Async(c => c.File("Logs/logs.txt")) .WriteTo.Async(c => c.Console()) .CreateLogger();

    await CreateHostBuilder(args).RunConsoleAsync();
}

Would imagine that there are no error logs for this as the problem is the produced code is not correct, or rather that the option to even choose this is missing.

[sumeyye.kurtulus] said: If, after the next Studio release, you still encounter blockers or regressions, we absolutely want to hear about them—preferably with concrete repro steps so we can act quickly.

As there have been at least two new releases of ABP Studio by now, is this fixed (we have not tried as we can't motivate testing every new release to see if it now works out of the box)? Thanks.

Seems like this footer is still displayed when running the API (.Host) project but only on error pages, not login pages for same URL etc.