Bug 32849 - ObjCRuntime.Messaging is still internal
Summary: ObjCRuntime.Messaging is still internal
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: XI 8.10
Hardware: PC Mac OS
: --- enhancement
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-08-06 22:31 UTC by Frank A. Krueger
Modified: 2017-09-28 08:37 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Frank A. Krueger 2015-08-06 22:31:53 UTC
When you all switched ObjCRuntime.Messaging to be internal with Universal, you said "something" would be made public so that we can bind to functions Xamarin still doesn't support.

But the class is still internal and inaccessible.

Very annoying.
Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-08-07 03:44:12 UTC
Quick hack: https://gist.github.com/rolfbjarne/981b778a99425a6e630c
Comment 2 Rolf Bjarne Kvinge [MSFT] 2017-09-28 08:37:37 UTC
We won't be adding public objc_msgSend P/Invokes to Xamarin.iOS.dll, you can copy-paste the ones from comment #1 into your own project and use those instead.