Thanks , I've already tried this approach but this time no hangfire jobs are registered. So for now I'll be waiting for the other issue solution I think. As a result of this topic , I understand that we shouldn't override a module if there isn't any problem, right ? Thank you.
Ok thank you, we'll be calling SetAsync() method before.
Actually I don't want to change options I want to change for example OnApplicationInitialization method behaviour because of an internal module error . I've also opened the issue related with this topic , you can check the specific case from below link :
https://support.abp.io/QA/Questions/2578/AbpBackgroundWorkersHangfireModule-exception-without-using-hangfire-configuration
But I'll try your module approach. Note => If the issue in the link above will be fixing , we don't even need to change the module.
Hello , Normally I shouldn't reach the entity repository like that from DDD manner , It's not a best practice. Because I should delete them from aggregate repository, so normally we don't have any repositories for entity itself. Anyway I've tried this approach , too. But it didn't work.
Ok, thanks for the information.
Is this the abp design or it comes from Ef core ORM usage ? Because normally when you directly listen table changes from sql we can catch the changes. I understand that abp's pre-built events do not support this cascade deletion , right ?
Hello , Is there any spesific reason to choose netstandard as target framework ? If we change all layers to .net5 , will we run into an unexpected error ?
Thank you.
Hello @ChetanKumbhar Did you solve this issue ? We have also same issue and same error with one of our project. Like below test log output:
<StdOut>[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v2.4.3+1b45f5407b (64-bit .NET 5.0.10) If you find a solution , could you please share with us ?
Thank you.
Hello , My question stands behind a little bit :) Is there anything new about the main issue ? I've shared the nuget 3rd party library lastly with you.
Thank you.