the application does NOT start if you delete appsettings.secrets.json
We don't check licenses in production but but development
Hi,
You can safely delete files, We don't check licenses in production
See: https://support.abp.io/QA/Questions/3999/license-error#answer-2481de64-16f7-6ff5-1166-3a077416ec17
You can see the document to know how to avoid publishing the appsettings.secrets.json: https://learn.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props#copytopublishdirectory
some advice about how to publish the migration project within the blazor project ( to prevent duplication of dll's ) and run it automaticly on blazor start would be great :)
Are you talking about database migrations?
You can use the execute database migrations on production environments: https://docs.abp.io/en/commercial/latest/startup-templates/application/solution-structure#dbmigrator-project
Please open a new ticket ,thanks.
ok
As you know, Kafka is a distributed message system, and messages can be consumed in parallel. Even if one message fails it will not affect the other.
You should not throw unhandled exceptions in the event handler, it keeps retrying in the system and blocks your other event handlers(In the outbox/inbox patterns, messages are sequential)
Your event handlers should be independent of each other, if one fails, you need to roll back all published events, you should place the code logic before publishing the event instead of an event handler
then how you will notify the UI Realtime if the consumer is fail during rollback event.
Same, Kafka is a distributed application, it can't show notify the UI in real-time, but you can build a real-time notification system(SignalR)
but still rollback is not working. even I manually throw exception to consumer.
When you successfully publish an event, it's not possible to rollback. you might consider posting a rollback event to rollback your changes
When you switch to an actual distributed event bus provider (e.g. Kafka or RabbitMQ), then the event handlers will be executed in different processes/applications as their purpose is to create distributed systems. In this case, the only way to implement transactional event publishing is to use the outbox/inbox patterns as explained in the Outbox / Inbox for Transactional Events section.
Hi,
You can see the document: https://docs.abp.io/en/abp/latest/Distributed-Event-Bus#transaction-and-exception-handling
You can consider redundant user data in the module like we did: https://github.com/abpframework/abp/tree/dev/modules/cms-kit/src/Volo.CmsKit.Domain/Volo/CmsKit/Users
The CMS is a module, Its user data is synchronized from the identity module.
At this point you can create navigation properties in the module
Hi,
As far as I know, it's not possible to create a navigation property in a different database.
You should create relationships through code logic.
