You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be worth discussing in limitations the apparent footgun with transaction scopes in that they do not support asynchronously committing or rolling back transactions.
In asp.net "async everything" is highly encouraged so the absence of await using or await scope.CompleteAsync() sent me down an internet rabbit hole trying to figure out if committing was blocking(yes of course).
This issue on dotnet seems to be requesting the API be extended for async complete/dispose: dotnet/runtime#1420 .
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: 1073c238-9389-d826-a696-f1108a4f2ce0
Version Independent ID: cf56babd-def0-d76e-8eee-e33341b6a009
It may be worth discussing in limitations the apparent footgun with transaction scopes in that they do not support asynchronously committing or rolling back transactions.
In asp.net "async everything" is highly encouraged so the absence of
await using
orawait scope.CompleteAsync()
sent me down an internet rabbit hole trying to figure out if committing was blocking(yes of course).This issue on dotnet seems to be requesting the API be extended for async complete/dispose: dotnet/runtime#1420 .
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: