Hi @maazq,
The class is moved to Volo.Abp.Account.Public.Web namespace.
Edit: This is not true actually. The blog post uses free Account module, and AbpAccountOptions is under different namespaces in Free & Pro Account modules. You need to use the one i mentioned above (Volo.Abp.Account.Public.Web).
@jhsanc
See https://github.com/abpframework/abp/issues/11505#issuecomment-1039854226
@Buckoge
For now, there is not planned date for a new patch of 5.1 release.
Hi @ElifKaya,
We've already fixed the issue. See https://github.com/abpframework/abp/pull/11556
It is not released yet, though.
Could you spot where exactly input.DateOfBirth lose its value?
Does this issue occur when you use a simple <input type='date' .../> instead of <abp-input... />?
Hi @bhasinp,
I have reproduced the issue & fixed it for the next patch. Also, your question credit is refunded.
Problem is that TenantDbContext is not modified during code generation. To fix it manually for now, you have to copy related code from DbContext to TenantDbContext file. Then re-generate migrations.
example codes to copy:
public DbSet<Author> Authors { get; set; }
builder.Entity<Author>(b =>
{
b.ToTable(MyProjectConsts.DbTablePrefix + "Authors", MyProjectConsts.DbSchema);
b.ConfigureByConvention();
b.Property(x => x.TenantId).HasColumnName(nameof(Author.TenantId));
b.Property(x => x.Name).HasColumnName(nameof(Author.Name));
});
May it be related with the following code?
Input.DateOfBirth = DateTime.Now;
return Page();
Then i don't think this is related with CLI or Suite. You can try cleaning you solution (deleting existing bin-obj folders) and check again.
By the way, we suggest you to use the same Suite version with your project. But this is unrelated with the issue.
Hi @ozgur.bassullu,
It seems like the file your solution informations are saved is somehow corrupted.
Path of the file is %UserName%\.abp\suite\appsettings.json. Can you change file content to with the following and try again?
{
"IsDotnetEfCoreToolInstalled": true,
"Solutions": [
]
}