From https://aspnetboilerplate.com/Pages/Documents/EventBus-Domain-Events#entity-changes:
'ing' events (e.g. EntityUpdating) are triggered before committing a transaction. This way, you can rollback the unit of work and prevent an operation by throwing an exception. 'ed' events (e.g. EntityUpdated) are triggered after committing a transaction, for which you cannot rollback the unit of work.
It seems more appropriate to add multiple IRealTimeNotifier (notifying users in a different ways) than multiple INotificationDistributor (deciding which users to distribute to).
Would multiple IRealTimeNotifier support your use case?
Support for multiple distributers was added in ABP 4.1.
Which version of ABP are you on?
You probably don't want distributers though: aspnetboilerplate/aspnetboilerplate#4326 (comment)
Don't pass invalid MaxResultCount, that's what validation makes sure doesn't happen. It defaults to 10 in LimitedResultRequestDto.
Allowing the client to disable pagination is really bad. But you can try to override MaxResultCount with a different validation or accept another bool property, and then decide whether to set it to int.MaxValue in your method.
From https://docs.aspnetzero.com/documents/zero/latest/Getting-Started-Core#run-the-project:
open a command prompt, navigate to root directory of *.Web.Mvc project and run npm run create-bundles command.
To access the ASP<span></span>.NET Zero private GitHub repositories, invite yourself to become a member of the ASP<span></span>.NET Zero organization using your GitHub username.
As mentioned twice, it's already fixed.
You can make the changes in the linked PR before the next release (v6.8).
So the table didn't exist?
Wow, the ads...
You have 13 <script> in <head>. See: Where to place JavaScript in an HTML file?
