Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 23050 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Implement TransactionScopeAsyncFlowOption for the TransactionScope class. TransactionScopeAsyncFlowOption has been added in .net 4.5.1
Yes, this is still a problem in Mono:
If you create a TransactionScope and inside is any async method, there is a danger of thread changing (just if the operation takes long) and the transaction scope is not going to work over threads.
"Transaction.Current has changed inside of the TransactionScope"
"The current TransactionScope is already complete"
For more info see:
Still nothing solved on this issue?