Preserve synchronization context in SaveChangesAsync for accepting changes #23971
Labels
area-save-changes
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Since #10164, we have
ConfigureAwait(false)
everywhere; this can cause issues in certain data binding scenarios, when accepting changes triggers a UI change, which is no longer executed on the UI thread (e.g. #22841).We could specifically use
ConfigureAwait(true)
in the code path leading to AcceptAllChanges (specifically in two places: DbContext.SaveChangesAsync, StateManager.SaveChangesAsync).The text was updated successfully, but these errors were encountered: