Activities of "maliming"

• ABP Framework version: 9.0
• UI Type: MVC

When you encounter problems in the development or production environment, we would like to see the log to troubleshoot the problem.

.MinimumLevel.Debug() will set MinimumLevel to Debug to show more logs.

We don't want to see EF Core's Debug logs when your problem has nothing to do with EF Core.

var loggerConfiguration = new LoggerConfiguration()
    .MinimumLevel.Debug()
    .MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning)
    .Enrich.FromLogContext()
    .WriteTo.Async(c => c.File("Logs/logs.txt"))

If you have an EF Core-related problem, you can remove MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning) and EnableSensitiveDataLogging to see EF Core debug logs.

Configure<AbpDbContextOptions>(options =>
{
    /* The main point to change your DBMS.
     * See also BookStoreMigrationsDbContextFactory for EF Core tooling. */
    Configure<AbpDbContextOptions>(options =>
    {
        options.Configure(actions =>
        {
            actions.UseSqlServer();
            actions.DbContextOptions.EnableSensitiveDataLogging();
        });
    });
});

If your API website experiences a JWT authentication problem, please ShowPII and output identity model logs.

 public async static Task<int> Main(string[] args)
{
    IdentityModelEventSource.ShowPII = true;

    IdentityModelEventSource.Logger.LogLevel = EventLevel.Verbose;
    var wilsonTextLogger = new TextWriterEventListener("Logs/identitymodel.txt");
    wilsonTextLogger.EnableEvents(IdentityModelEventSource.Logger, EventLevel.Verbose);

See: https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/wiki/PII https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/wiki/How-to-log-from-IdentityModelEventSource.Logger

If you have an OpenIddict related problem, please override the OpenIddict log level to Verbose.

var loggerConfiguration = new LoggerConfiguration()
    .MinimumLevel.Debug()
    .MinimumLevel.Override("Microsoft.EntityFrameworkCore", LogEventLevel.Warning)
    .MinimumLevel.Override("OpenIddict", LogEventLevel.Verbose)
    .Enrich.FromLogContext()
    .WriteTo.Async(c => c.File("Logs/logs.txt"))

This error is related to NET 9 SDK.

You can use a specific SDK version in a folder to install the abp suite.

> dotnet --list-sdks
8.0.401 [/usr/local/share/dotnet/sdk]
9.0.100-rc.2.24474.11 [/usr/local/share/dotnet/sdk]

> cd TestFolder
TestFolder > dotnet new globaljson --sdk-version 8.0.401

TestFolder > dotnet --version
8.0.401

TestFolder > abp suite

Update:

Please use latest official NET 9 SDK to solve this issue,

Report from https://github.com/abpframework/abp/issues/7951

Version: ABP Suite 4.2.1 User Interface: MVC Database Version: EF Core Javascript Alert: DataTables warning: table id= Table - Requested unknown parameter '.uOM' for row 0, column 5. For more information about this error, please see http://datatables.net/tn/4 Steps needed to reproduce the problem

1. Create an entity that has a property the has all capital letters (UOM for unit of measure)
2. Generate the Entity including the MVC UI
3. Start a debug instance
4. Click on the tab that contains the new entity
5. This alert should pop up

The reason this occurs is that the variable in the datatable gets generated as ".uOM" whereas the actual value in the object is ".uom". To fix you simply change the variable in the dataTable to "******.uom"

Not a neck breaking bug but ever so slightly annoying

Do not share the ABP source code and your private NuGet API key If there is a need, please share it to our support staff via email info@abp.io

Update the ABP CLI:

dotnet tool update -g Volo.Abp.Cli

Update the ABP Suite:

abp suite update or dotnet tool update -g Volo.Abp.Suite

• Release notes https://docs.abp.io/en/commercial/latest/release-notes

Update the ABP CLI:

dotnet tool update -g Volo.Abp.Cli

Update the ABP Suite:

abp suite update

• Release notes: https://docs.abp.io/en/commercial/latest/release-notes