Hi @fastsoft,
Have you checked the related document?
https://docs.abp.io/en/commercial/4.3/modules/account/ldap
Have you added Hangfire namespace to MyProjectHttpApiHostModule file?
using Hangfire;
Hi,
I've tested and confirmed this bug. It will be fixed in next patch.
I've refunded your question credit. Thank you.
Hi,
Which project did you installed Volo.Abp.BackgroundJobs.HangFire package?
As i said, this is by design. So don't expect it to be changed in future.
Hi,
Only the setting contributor page is on Blazor UI. For other pages, you are redirected to Host MVC UI.
Hi @christophe.baille
The first problem you mentioned (Firefox-Chrome) will be fixed in next patch. (Already fixed and waiting for release)
We'll check the second one (Language problem) and fix it in next patch as well.
Hi @viswajwalith
Yes, it is better to have different Rabbit MQ. Otherwise Events will be confused.
If you must use the same Rabbit MQ, at least you need to use different ExchangeName.
See https://docs.abp.io/en/abp/latest/Distributed-Event-Bus-RabbitMQ-Integration#configuration
Hi @petri.uusitalo
This is by design. And this is also same for Angular UI, even same for tiered MVC projects. You are redirected to MVC UI of .HttpApi.Host project for login.
However based on your website (https://commercial.abp.io/modules/Volo.Account.Pro) it says that Account module also supports Blazor UI Framework
This doesn't mean Account module doesn't support Blazor/Angular UI.
You are right. I've created an internal issue for this. We will fix this in next patch.
Thanks for reporting. Your question credit is refunded.
