Activities of "EngincanV"

Hi @Qusai,

and the BackGround worker does it execute (DoWorkAsync) everytime the timer starts ? lets say im executing something that will take alot of time and the timer is set to 1 minute , will it still execute the (DoWorkAsync) ? or will it wait until the first execution is done and then count another 1 minute ?

It waits until the first execution is done but does not count another 1 minute again. For example: Just assume you set your timer as 10 minute and it first called at 1.10pm, and assume your job finished at 1.22pm (took 12minutes, more than our period). The counter will not count from that point it will only count extra 8 minutes to complete your period (10 minutes) and run your worker.

Hi @uyarbtrlp, as I see your problem is resolved so I close the question. If your problem is not resolved yet, please don't hesitate to re-open it.

Hi @Shoba24, Can you share your *.cshtml.cs file?

Hi, Can you change your UseSwaggerUI middleware as follows?

app.UseSwaggerUI(options => 
{  
    // builds a swagger endpoint for each API version  
    foreach (var description in provider.ApiVersionDescriptions)  
    {  
        options.SwaggerEndpoint($"/swagger/{description.GroupName}/swagger.json", description.GroupName.ToUpperInvariant());  
    }  
    
    var configuration = context.GetConfiguration();
    options.OAuthClientId(configuration["AuthServer:SwaggerClientId"]);
    options.OAuthClientSecret(configuration["AuthServer:SwaggerClientSecret"]);
}); 

Hi @drg_tverkroost, AbpHelper.GUI is not our product, it's an open-source application. Can you create an issue on https://github.com/EasyAbp/AbpHelper.GUI?

knowing that there is 1 million records in this table for each one of the Tenants.

Could your problem be related with this https://stackoverflow.com/a/65440387/10477283?

With version 4.4, EntityFrameworkCore.DbMigrations project has been removed and DbContexts are unified. You can check this community article to understand the circumstances under that. If you were migrated your application from 4.3 to 4.4 please apply the steps in the article to unify your db context.

Can you examine your db context class inherit from ISaasDbContext or not?

[ReplaceDbContext(typeof(IIdentityProDbContext))]
[ReplaceDbContext(typeof(ISaasDbContext))] //ensure this line is exists
[ConnectionStringName("Default")]
public class MyDbContext : 
        AbpDbContext<MyDbContext>, 
        IIdentityProDbContext,
        ISaasDbContext //ensure this line is exists
{
    //...
}

You're welcome. I am closing the question since your problem is resolved.

Can you check your YourEntityFrameworkCoreModule depend on AbpSettingManagementEntityFrameworkCoreModule?

//other dependent modules
[DependsOn(typeof(AbpSettingManagementEntityFrameworkCoreModule))] //check this line exists or not
public class YourEntityFrameworkCoreModule : AbpModule
{
    //...
}

[ReplaceDbContext(typeof(IIdentityProDbContext))]
[ReplaceDbContext(typeof(ISaasDbContext))]
[ConnectionStringName("Default")]
public class YourProjectDbContext : 
    AbpDbContext<YourProjectDbContext>, 
    IIdentityProDbContext,
    ISaasDbContext
{
    //...
    
    protected override void OnModelCreating(ModelBuilder builder)
    {
        base.OnModelCreating(builder);
        builder.ConfigureSettingManagement(); //check this line exists or not
        
        //other configurations (e.g. builder.ConfigureAuditLogging())
    }
}

Hi @radhikashrotre, what is your ABP Framework version?