Azure and Microsoft recommend the use of retry functionality when accessing databases in the cloud. When trying to use sqlOptions.EnableRetryOnFailure() in an ABP project, it causes OpenIddict inside ABP to misbehave due to the database queries not being wrapped in a way that allows the auto-retry to function. As a result, either we have to wrap each and every database use in the application, or not use retry functionality at all. Neither is a viable solution for a production environment in the cloud.
In responce i tried to work around it by having 2 DBContexts pointing to the same database, one for the tools, the other with auto retry for our own code. Sadly this then failed to resolve DBContexts to i assume this is not a possible route either.
Is there a viable workaround for this hat we are not aware of? Otherwise we will have to stop using ABP altogether just for being incompatible with cloud stability. Resouces referenced: No Support 1 No support 2 No Support 3 Microsoft Recommendations
