Activities of "ageiter"

What really annoys me when working in the Suite is the pop-up that appears after saving. A toast notification would be enough.

Sometimes I go through all the entities and make a few changes, save them, and want to move straight on to the next one without having to click OK every time. For example, when I enabled ‘Remove unused usings’ for all of them.

Thank you for all your replies. For most things, I can wait for the next release.

One more question regarding your reply:

About RemoveUnusedUsings: Suite keeps the cleanup only if the solution builds after it. Apply the template change from my previous reply, make sure the solution builds, then generate the entity again. Existing .Extended.cs files are excluded from this cleanup because they contain your own code, so you can clean up their unused usings in your IDE.

Is this only the case when generating via the UI, or does it do the same when I trigger the generation via the CLI? abp suite generate -e $file.FullName -s $SolutionPath Or should it work even then, and is the only problem I’m having that it couldn’t be compiled?

Sorry for all the different findings. I’d like to help improve the product. I’ve deliberately split it into six separate posts so that you can reply to them more easily. Thank you very much.

One more thing: Why is a required navigation property now made nullable?

It's a master entity with two navigation properties (1:n). Both are required. In version 10.4, this was generated correctly.

Unfortunately, there’s another error… when generating EfCore…Repository.cs, there’s a mix-up with the using statements:

I couldn’t figure out what was causing the problem. The template appears to be the same as before (I haven’t customised anything here). Nor did the RemoveUnusedUsings parameter have any effect when I set it to false.

The Const files are overwritten each time. Would it be possible to introduce Extended files here as well, so that we can store our own constants?

To this end, changes are made to the formatting in the extended file (which do not comply with our style guidelines).

I have seen this in the following classes:

Domain:

  • Entity.Extended.cs
  • EntityManager.Extended.cs

One more thing I’ve noticed. I think the new feature “RemoveUnusedUsings”: true doesn’t seem to be working. I’ve set it to true, but I still have a lot of unused usings after generation.

Here are a few examples (this list is not complete):

Great thank you!

One more request: I’ve created a base class for the two DbContexts (Host & Tenant) and moved the shared EF model definition there (I don’t like duplicate code). And for tables that I only want in the Hosts database, I still have the option of defining them there alone.

As these are table definitions, I otherwise see a risk that discrepancies could arise if a manual change is made, because the change is only made in one place.

Could you please consider whether you might want to do the same for the generated code?

public abstract class BpoDbContextBase<TDbContext> : AbpDbContext<TDbContext>
    where TDbContext : DbContext
{ 
... 
}
[ConnectionStringName("Default")]
public class BpoDbContext : BpoDbContextBase<BpoDbContext>
{
    public DbSet<Kunde> Kunden { get; set; } = null!;

    public BpoDbContext(DbContextOptions<BpoDbContext> options)
        : base(options)
    {
    }

    protected override void OnModelCreating(ModelBuilder builder)
    {
        builder.SetMultiTenancySide(MultiTenancySides.Both);
        base.OnModelCreating(builder);

        // Configure mappings like that for the entities only available in the host side, but should not be in the tenant databases.

        if (builder.IsHostDatabase())
        {
            builder.Entity<Kunde>(b =>
            {
                b.ToTable(BpoConsts.DbTablePrefix + "Kunde", BpoConsts.DbSchema);
                b.ConfigureByConvention();
                b.Property(x => x.Kundennummer).HasColumnName(nameof(Kunde.Kundennummer));
                b.Property(x => x.Name).HasColumnName(nameof(Kunde.Name)).IsRequired().HasMaxLength(KundeConsts.NameMaxLength);
            });
        }
    }
}
[ConnectionStringName("Default")]
public class BpoTenantDbContext : BpoDbContextBase<BpoTenantDbContext>
{
    public BpoTenantDbContext(DbContextOptions<BpoTenantDbContext> options)
        : base(options)
    {
    }

    protected override void OnModelCreating(ModelBuilder builder)
    {
        builder.SetMultiTenancySide(MultiTenancySides.Tenant);
        base.OnModelCreating(builder);
    }
}

Could you make these test classes (such as the one mentioned above) partial in future, so that we can add our own extended class for further tests? I’ve now had to adapt this in my template.

Showing 1 to 10 of 347 entries
Boost Your Development
ABP Live Training
Packages
See Trainings
Mastering ABP Framework Book
The Official Guide
Mastering
ABP Framework
Learn More
Mastering ABP Framework Book
Made with ❤️ on ABP v10.8.0-preview. Updated on November 16, 2026, 06:26
1
ABP Assistant
🔐 You need to be logged in to use the chatbot. Please log in first.