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 34056 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
Regarding bug #34027, I brought up a suggestion on how to fix this. But it doesn't result in any improvements:
Atsushi Enomoto [1:59 PM]
Do you guys think importing TPL DataFlow sources from corefx (not referencesource) is good or bad idea? So far I have no idea if the API is different or not.
Marek Safar [2:22 PM]
TPL DataFlow has official nuget. I don’t think we need to build it (edited)
Atsushi Enomoto [2:59 PM]
Oh interesting. But the problem is that we do ship that assembly and people hit some bugs. https://bugzilla.xamarin.com/show_bug.cgi?id=34027
No more arguments followed.
At this state, it seems that mono should remove System.Threading.Tasks.DataFlow and let people use the ones in the PCL.
I think it is not always good because if there is any open source projects that are distributed as part of some Linux systems (because PCL are distributed as binary) it is going to be problematic. But maybe that's not Mono's responsibility.
Anyways if we don't do anything, that's the worst.