Activities of "enisn"

Hi,

It seems there is cache problem, can you try cleaning all the nuget cache and install abp suite standalone.

dotnet nuget locals all --clear

Install/update abp cli:

dotnet tool update --global Volo.Abp.Studio.Cli

Then try to open abp suite

abp suite

⚠️ Make sure you're logged in ABP CLI or ABP Studio. you can check if you're authenticated or not via following command:

abp login-info

If you're not logged in, use abp login command

Hi,

It seems there is no built-in way to retrieve it. But you can override SettingProvider in your application and add another method that applies your custom query by using re https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.Settings/Volo/Abp/Settings/SettingProvider.cs

but still you won't be able to access to data source directly to apply a custom query with value, you can also override on of the existing Setting Value Providers https://abp.io/docs/9.0/framework/infrastructure/settings#setting-value-providers

which is TenantSettingValueProvider in this case: https://github.com/abpframework/abp/blob/dev/framework/src/Volo.Abp.MultiTenancy/Volo/Abp/MultiTenancy/TenantSettingValueProvider.cs

Or you can create your own value provider according to your custom requirements and configure it:

Configure<AbpSettingOptions>(options =>
{
    options.ValueProviders.Add<CustomSettingValueProvider>();
});

Hi @richardf

Our angular team will help you on this issue.

Until the you can check this documentation if it helps: https://abp.io/docs/latest/framework/ui/angular/component-replacement

You can create different unit of work scopes and do not wait the second one for returning resposne of the http request. That might be the case.

Also if you don't need, you can disable unit of work only for your handler side. But still, handling operation will be executed sync in the same thread, whenever you use Task.Run, you detach the the thread from the original one and you don't have to wait it. It logically works as expected but whenever an error occurs in the created task, it'll be harder to track it.

By the way, you can manually control unit of work according to your requirements: https://abp.io/docs/latest/framework/architecture/domain-driven-design/unit-of-work#controlling-the-unit-of-work

There is no exact same feature in ABP, but there are alternatives:

You can use Entity Extensions: https://abp.io/docs/latest/framework/architecture/modularity/extending/module-entity-extensions

It allows you easily to add extra properties to existing enities from existing modules and customize them.

Even you can map those newly added properties to a new column in the database: https://abp.io/docs/latest/framework/architecture/modularity/extending/customizing-application-modules-extending-entities#entity-extensions-ef-core

Hi,

It seems there is no support for pushing a new component into the routes collection via using route.provider.ts

But as another option, you can replace the menu component and render the menus on your own logic:

https://abp.io/docs/latest/framework/ui/angular/component-replacement?_redirected=B8ABF606AA1BDF5C629883DF1061649A#layout-components

Hi,

Everything looks good except ABP Studio CLI.

Can you find the ABP Studio logs and share with us to find the problem. The logs are located yourusername/.abp/studio/ui/logs folder by default.

To overcome the PingOne authentication problem in ABP, my primary suggestion is to meticulously review your ABP application's authentication configuration against your PingOne application settings. Double-check that the Client ID, Client Secret, Authority URL, and Response Type in your ABP application perfectly match those configured in PingOne. Furthermore, investigate **claim mapping **within ABP to ensure that user attributes from PingOne are correctly translated and recognized by your ABP application for proper user login and authorization. Debugging the redirection flow and reviewing any logs during the authentication handshake can also pinpoint configuration mismatches.

If it helps, this article can be a good example for claim mappings: https://abp.io/community/articles/how-claim-type-works-in-asp-net-core-and-abp-framework-km5dw6g1

Thanks for your answer, we'll investigate if there is a breaking-change and update migration guide if necessary

You ticket is also refunded

Hi,

Can you provide any insights or suggestions to improve the performance? is await Task.Run(async ()).. is required? is seperate ouw required inside the handler?

If you need to execute main process and the event itself in a same transaction, then no, you cannot make it faster by executing in a different thread since the roll-back won't work whenever you use Task.Run. All the local events are designed to be runned in the same transaction.

But if you don't need to execute in the same transaction, you can use IDistributedEventBus with RabbitMQ or Kafka. In that case you can use Inbox/Outbox Pattern to ensure all the events are consistently published and consumed. If your application goes bigger, that might be a good scenario for you