Use ContinueWith rather than finally for coroutine result types #4669
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
When run in PowerShell with MTA (multi-threaded apartment) enabled, the
RunOnMTA
methods have an optimization to run directly rather than spinning up a new thread. This optimization used afinally
to callComplete
, but aTask
will be returned (and the finally executed) before the task is completed. This resulted in a completed collection and errors when attempting to add more messages to it.Change
Use
ContinueWith
andExecuteSynchronously
to effectively make afinally
for theTask
result object. Convert the existingfinally
to only callComplete
on exception.Validation
Manually confirmed the -MTA case with
Invoke
andStart
/Complete
command use cases.Microsoft Reviewers: Open in CodeFlow