But where can I get the update?
After we've updated the EasyCrm application, we'll inform you.
Can you create a new question and explain it in detail?
I posted a new ticket here https://support.abp.io/QA/Questions/2749/Getting-json-errors-while-deploying-code-on-testing-server
Thanks @safi, I close this issue since it's resolved.
No I didn’t have any extra properties
Thanks, I will test and inform you asap.
Hi @learnabp, I will test it and write you back asap. Did you add any extra properties to your Plan entity?
Why always auto close the ticket?
Hi @GerryGe, we generally close a ticket, when we create an issue for a problem in our internal repository, in another word when we take an action about the problem. We've created an issue for your question and keep it open until it is fixed.
Sorry for the misunderstanding. Best regards.
Hi, you don't need to inherit your repository class from the IRepository<TEntity, TKey> interface. If you remove it, you don't get the DependencyResolutionException.
Hi @agilmore, can you check the source-map version? (you can see the version from yarn.lock file)
Hi, can you add the Volo.Abp.Http.Client.Web package to your *.Web.Host project?
<ItemGroup>
<PackageReference Include="Volo.Abp.Http.Client.Web" Version="5.1.1" />
</ItemGroup>
[DependsOn(
//...
typeof(AbpAccountAdminWebModule),
typeof(AbpSwashbuckleModule),
typeof(AbpAspNetCoreSerilogModule),
typeof(AbpHttpClientWebModule) //add this line
)]
public class MyAppWebHostModule : AbpModule
{
//...
}
Hi @ldacnfinit, can you try to create a UOW in your ImportByExcelFile method manually, like below:
private readonly IUnitOfWorkManager _unitOfWorkManager;
public virtual async Task> ImportByExcelFile(IFormFile file)
{
using (var uow = _unitOfWorkManager.Begin(requiresNew: true, isTransactional: true))
{
//...
await _identityUserManager.CreateAsync(ObjectMapper.Map(s), userPwd, false);
await uow.CompleteAsync();
}
}
https://docs.abp.io/en/abp/latest/Unit-Of-Work#begin-a-new-unit-of-work
Hi @shobhit, I suggest you to controlled upgrade your application to v5.1, which means first upgrade to v4.3 and then v4.4 and then so on.
You can follow the following migration guides to see the breaking changes and additional notes:
Also, you can read the blog posts to see the new features by version, from our blog website.
What are the latest features in 5.1
You can read the new features that come with v5.1 from here.