The only way to make it work, it is to add the reference of Blogging.Application.Contracts.Shared to my domain project, which will make the architecture not clean again...
Hi
Maybe you can reference of Blogging.Application.Contracts.Shared to DbMigrator. then move your IDataSeedContributor to DbMigrator project.
hi
https://github.com/IdentityServer/IdentityServer4/issues/4535 https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/proxy-load-balancer?view=aspnetcore-5.0
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;
});
