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 on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
CFMessagePortCreateRemote and CFMessagePortSendRequest are missing bindings.
What about CFMessagePortRef, CFMessagePortCreateLocal(),
CFRunLoopSourceRef, CFMessagePortCreateRunLoopSource(), CFRunLoopAddSource(),
CFRunLoopGetCurrent(), kCFRunLoopCommonModes, etc ?
Some of those are already about in CoreFoundation.CFMessagePort class.
But yes, we need to do a scrub of all the CFMessage* classes to verify we have bindings.
The entire support was implemented the day this bug was filed, we just did not cross-reference this.
On maccore: 37f35a6f25a7e28aed34fb36bf67e29c0341c4dd and by extensoin xamarin-macios