Activities of "liangshiwei"

How can we make background job work in the same transaction with our business code; so it will not created or rolledback when we get any error on method completion (CompleAsync)

Hi,

I'm sorry to say, Background jobs are independent of application threads, so they cannot use the same transaction.

You can try this:

public async Task CreateAsync()
{
    using (var uow = _unitOfWorkManager.Begin(requiresNew: true, isTransactional: true))
    {
        //...
        await productRepository.InsertAsync(new Product("Product1"));
        await uow.CompleteAsync();
    }
            
    await backgroundJobManager.EnqueueAsync(ProductJobArgs);
}

Hi,

You can check these documents: https://docs.abp.io/en/abp/6.0/Migration-Guides/Abp-6_0 https://docs.abp.io/en/commercial/6.0/migration-guides/v6_0

Hi,

Can you share the steps to reproduce and share some screenshots? thanks

Hi,

Actually, this is not related to ABP

You can see the dicussion on Rebus: https://github.com/rebus-org/Rebus/issues/492

Hi,

Sorry that I could not reproduce the problem

Can you share a project with me via email? shiwei.liang@volosoft.com thanks

Hi,

Can you share the steps to reproduce?

Hi,

I'm sorry about that, yes, the initial loading performance is a problem, we are always trying to improve performance.

But it actually not an ABP problem, this is a limitation of Blazor WebAssembly application.

If you really care the loading performance, I recommend you use Blazor-Server.

Download size is significantly smaller than a Blazor WebAssembly app, and the app loads much faster.

See: https://docs.microsoft.com/en-us/aspnet/core/blazor/hosting-models?view=aspnetcore-6.0

Hi,

Could you share a project with me via email? shiwei.liang@volosoft.com

I will check it. thanks.

ok

Hi,

You can share a project with me via email, and I can check it soon.