Activities of "EngincanV"

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?

• Add the following line to your .csproj file:

<ItemGroup>
    <PackageReference Include="Volo.Abp.Http.Client.Web" Version="5.1.1" />
</ItemGroup>

• Add DependsOn[typeof(typeof(AbpHttpClientWebModule))] to your *WebHostModule class:

[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:

• Framework - 4.x to 4.3
• Commercial - 4.x to 4.3
• Framework - 4.x to 5.0

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.

Hi, with v5.1 Angular 13 is supported and v5.1 ABP Startup Templates use Angular 13.

https://blog.abp.io/abp/ABP.IO-Platform-v5-1-Has-Been-Released

Hi @selinkoykiran, your problem will be resolved with this PR.

Hi @SouravParia, we have a sample project named StoredProcedureDemo, maybe you can check AppUserRepository.cs in this sample project.

• In the sample project there is not any parameter passed to the stored procedure and you can update the related part like below.

using (var command = CreateCommand("<your_stored_procedure_name>", CommandType.StoredProcedure, new SqlParameter[] { /* your parameters: E.g. new SqlParameter("id", id) */ }))
{
    //your logic...
}

Configure<AbpAntiForgeryOptions>(options =>
{
    options.AutoValidateIgnoredHttpMethods.Remove("GET"); //auto validate for GET requests
});

After I've configured the AbpAntiForgeryOptions as above, I could not send a successful GET request to my endpoints unless I provide a RequestVerificationToken header.

But if there is an interceptor and passes a RequestVerificationToken on behalf of me, I can successfully make a GET request as follow. (And we do it on Swagger UI)

So can you try to navigate the URL of one of your GET requests on the browser? I am not sure but "burpsuite" might be intercepting the request and passing the RequestVerificationToken automatically (maybe you can check the header that it passed).