Hi,
I found the problem because you are using tiered architecture. that means it is a front-end and back-end separation architecture.
When you call the CreateAsync
method of customersAppService
class, It's actually a dynamic HTTP proxy, making requests using HttpClient. see: https://docs.abp.io/en/abp/latest/API/Dynamic-CSharp-API-Clients
So, you need to change the current tenant in the AppService instead of UI code.
SqliteConnection does not support nested transactions
Try disabled transaction for unit tests:
Configure<AbpUnitOfWorkDefaultOptions>(options =>
{
options.TransactionBehavior = UnitOfWorkTransactionBehavior.Disabled;
});
Hi,
Ok, I hope I can help you solve the problem quickly.
Could you provide the full steps to reproduce? thanks.
Hi,
I can reproduce the problem and will create an internal issue to fix it, BTW your ticket was refunded.
Hi,
Ok, I will try to reproduce the problem.
Hi,
When you create a new project, the ABP suite will build the project, try to restore libs, and create initial migration files. so yes, it will lock the file and take a while(not long)
You need to wait until these steps are finished, then you can open the solution in VS2022 and do anything.
Hi,
Could you share the steps to reproduce? thanks.
Hi,
We have a question for this before: https://support.abp.io/QA/Questions/3209/ABP-DbMigrator---Reverting-last-database-update-migration
Unfortunately, we won't be adding this feature.
Hi,
You can try this:
Install the
System.Data.SqlClient
package version with 4.8.3
using (var transaction = new TransactionScope())
{
await productRepository.InsertAsync(new Product("Product1"));
await backgroundJobManager.EnqueueAsync(ProductJobArgs);
transaction.Complete();
}
Here is my test image:
Hi,
We create an internal issue for this and will check it.