hi
I think this limitation has nothing to do with CORS, it is a browser limitation.
Did you changed the TenantKey ?
services.Configure<AbpAspNetCoreMultiTenancyOptions>(options =>
{
options.TenantKey = "__tenantId";
});
hi BassaSolutions
Can you share a simple project? liming.ma@volosoft.com
hi
Can you try to add the AbpAccountClaimsPrincipalFactory?
https://github.com/abpframework/abp/issues/8888#issuecomment-833167705
hi
You can consider to use IAsyncQueryableExecuter, it's target to netstandard2.0.
https://docs.abp.io/en/abp/latest/Repositories#option-3-iasyncqueryableexecuter
hi
Maybe you can try show the meessage on its events. For example, onClose.
https://docs.abp.io/en/abp/latest/UI/AspNetCore/Modals#functions https://docs.abp.io/en/abp/latest/UI/AspNetCore/Modals#events
hi
https://github.com/abpframework/abp/issues/9366#issuecomment-869247128
hi
SqliteConnection does not support nested transactions.
You can disable the transaction in unit test, This is a limitation of sqlite, we can only do this.
Configure<AbpUnitOfWorkDefaultOptions>(options =>
{
options.TransactionBehavior = UnitOfWorkTransactionBehavior.Disabled;
});
hi Because Microsoft's EntityFrameworkCore also only supports net standard 2.1.
hi
I think you can customize a IOptions implementation, You can refer to OptionsMonitor.
IOptions<FhirOptions>
