Activities of "maliming"

hi

On five occasions, while using abp Suite, my computer has given the dreaded green screen of death. The only other application open was WSL Ubuntu running redis and visual studio. Any idea why?

You can check the error event logs in the Event Viewer of windows.

The platform is excruciatingly slow compared to a previously built application using the same database. I even built a new database to see if it was the amount of data, but it is just as slow with only row of data. This is without any major modifications to your code. All I have done is generate crud tables and build. Is there some fine tuning that needs to be done? Half the time I attempt to build a project I get an error saying IIS is not able to run because a file is locked. Why is this happening? I have never had this happen using visual studio before.

Please share full request & error logs(Logs.txt). Thanks.

You can set the log level to Debug to see more logs.

 public async static Task<int> Main(string[] args)
    {
        Log.Logger = new LoggerConfiguration()
            .MinimumLevel.Debug()
            .Enrich.FromLogContext()
            .WriteTo.Async(c => c.File("Logs/logs.txt"))
            .WriteTo.Async(c => c.Console())
            .CreateLogger();

hi

Please share the detailed error log(Logs.txt).

hi

Can you share some code to reproduce?

Had you checked the cache on Redis?

hi

Please share the full error stack.

What's your abp version?

I guess you are using the Identity Server. right?

hi

Begin a New Unit Of Work in your HandleValidSubmit method

https://docs.abp.io/en/abp/latest/Unit-Of-Work#begin-a-new-unit-of-work

Thanks

sure.

What is your azure environment? Can you introduce it?

It's not released yet, please wait for 7.1.1

hi

This is a problem with EF Core, Here is my test code with pure EF Core.

using Microsoft.EntityFrameworkCore;
using Microsoft.EntityFrameworkCore.Design;

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddDbContext<ApplicationDbContext>(options => options.UseSqlServer("Server=(localdb)\\mssqllocaldb;Database=WebApplication1;Trusted_Connection=True;MultipleActiveResultSets=true"));

public class Employee
{
    public int Id { get; set; }
    public string Name { get; set; }
}

public class Employee2
{
    public int Id { get; set; }
    public string Name { get; set; }
}

public class ApplicationDbContext : DbContext
{
    public ApplicationDbContext(DbContextOptions<ApplicationDbContext> options)
        : base(options)
    {
    }

    protected override void OnModelCreating(ModelBuilder builder)
    {
        builder.Entity<Employee>(b =>
        {
            b.ToTable("Employee", schema: null);
            b.Property(x => x.Name).IsRequired().HasMaxLength(100);
        });

        builder.Entity<Employee2>(b =>
        {
            b.ToTable("Employee", schema: null);
            b.Property(x => x.Name).IsRequired().HasMaxLength(100);
        });

        base.OnModelCreating(builder);
    }
}

public class ApplicationDbContextFactory : IDesignTimeDbContextFactory<ApplicationDbContext>
{
    public ApplicationDbContext CreateDbContext(string[] args)
    {
        var optionsBuilder = new DbContextOptionsBuilder<ApplicationDbContext>();
        optionsBuilder.UseSqlServer("Server=(localdb)\\mssqllocaldb;Database=WebApplication1;Trusted_Connection=True;MultipleActiveResultSets=true");

        return new ApplicationDbContext(optionsBuilder.Options);
    }
}

We will fix the issue in the next patch version, You question credit refunded.