hi
There is no function related to JSON serialization in abp's hangfire.
Maybe you can create a service to handle JSON serialization/deserialization.
hi @alexander.nikonov
Can you use the template project to reproduce the problem and share it with me? liming.ma@volosoft.com
The reason for this situation may be that the __EFMigrationsHistory
table is empty after the first execution of DBMigrator.
hi kirtik
You can try this.
protected override void OnModelCreating(ModelBuilder builder)
{
base.OnModelCreating(builder);
/* Include modules to your migration db context */
builder.ConfigurePermissionManagement();
builder.ConfigureSettingManagement();
builder.ConfigureBackgroundJobs();
builder.ConfigureAuditLogging();
builder.ConfigureIdentity();
builder.ConfigureIdentityServer();
builder.ConfigureFeatureManagement();
builder.ConfigureTenantManagement();
builder.UseCosmos();
/* Configure your own tables/entities inside the ConfigureBookStore method */
builder.ConfigureBookStore();
foreach (var entityType in builder.Model.GetEntityTypes())
{
ConfigureETagConcurrency(builder, entityType);
}
}
private void ConfigureETagConcurrency(ModelBuilder modelBuilder, IMutableEntityType mutableEntityType)
{
if (mutableEntityType.IsOwned())
{
return;
}
if (!typeof(IEntity).IsAssignableFrom(mutableEntityType.ClrType))
{
return;
}
var entityTypeBuilder = modelBuilder.Entity(mutableEntityType.ClrType);
if (entityTypeBuilder.Metadata.ClrType.IsAssignableTo<IHasConcurrencyStamp>())
{
entityTypeBuilder.Property(nameof(IHasConcurrencyStamp.ConcurrencyStamp))
.IsETagConcurrency()
.HasMaxLength(ConcurrencyStampConsts.MaxLength)
.HasColumnName(nameof(IHasConcurrencyStamp.ConcurrencyStamp));
}
}
If I cannot reproduce the problem, I cannot solve the problem. : (
hi
I mean can you find some differences between your project and the template project that might be causing the problem.
That is, if you copy some code of your project to the template project, the above problem occurs.
hi shobhit
Can you reproduce the problem in the 4.0 template project? You can try it. In that way I can quickly locate the problem.
hi @shobhit
Can you reproduce the problem in the 4.0 template project? Because I see you are using different connection strings for different modules.
https://docs.abp.io/en/abp/latest/Entity-Framework-Core-Migrations
Please back up the code and database.
dotnet ef migrations add Initial
command in xxx.EntityFrameworkCore.DbMigrations
folder.dotnet ef database update
command or run xxx.DbMigrator
to apply.https://docs.microsoft.com/en-us/ef/core/managing-schemas/migrations/
hi kirtik
I will check as soon as possible. : )