Activities of "maliming"

hi

Can you try the test code in the latest template?

If still slow please share the project with me liming.ma@volosoft.com

Good news

hi

How do I enable the new service to use an isolated database on microservice template?

https://docs.abp.io/en/commercial/5.3/startup-templates/microservice/infrastructure#hosting

hi

Can you add the addTagHelper code to the project that contains this code? If still does not work. Please share a minimum project. liming.ma@volosoft.com

hi @alexander

Unfortunately, I cannot share the source code

Please use the template project to reproduce the problem and share it liming.ma@volosoft.com

hi

Can you check your NuGet.Config file?

"C:\Users\username\AppData\Roaming\NuGet\NuGet.Config"

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="nuget" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
</configuration>

hi

dotnet tool install --global Volo.Abp.Cli --add-source https://api.nuget.org/v3/index.json

Also try this.

Configure<AbpClaimsServiceOptions>(options =>
{
    options.RequestedClaims.AddRange(new[]{ "SocialSecurityNumber" });
});

hi

Can you share a new access_token?

hi

So if I understand correctly, exceptions like AntiForgery and DependencyResolutionException are returned with statuscode 400?

DependencyResolutionException should be get 500, the AntiForgery will get 400.

Many validation errors will use 400 code, eg: Parameter validate error. AntiForgery token. etc.

This behaviour is unwanted for certain endpoints. For example a webhook, called from Azure event grid, to push messages. When event grid receives a 400, it won't retry the message. At a 500 it does.

400 means the request info has something wrong. You should check the Azure request.