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.
Making Messaging non-public breaks years of code.
I have always been able to rely on the Messaging class to work around missing APIs and such in MonoTouch. Now that the class is non-public, I have to write even worse workarounds.
PLEASE make it public again. Now I have to write my own class that mimics your Messaging. :-(
Why break backwards compatibility for no gain?
Class klass = new Class ("UIScreen");
_hasScreens = ObjCRuntime.Messaging.bool_objc_msgSend_IntPtr (klass.Handle, Selector.GetHandle ("respondsToSelector:"), Selector.GetHandle ("screens"));
They are generated code and appears (fine) and _disappears_ (problematic for public API) as needed. Also making them public has prevented us from making changes/optimizations to the internals.
We do have plans to make an helper (optional) assembly (.dll) that will contains the same functionality (and likely the API, with or without, simpler alternatives).
Created attachment 9293 [details]
unofficial messaging dll
OK, thanks for looking into it. On further reflection, I was able to remove most of my uses so it's not as important as I worried it would be.
No problem, many people had the same initial reaction :-). Most of the uses we have seen so far are generally hacks (that we often provided) around old MT bugs or to enable missing features (that were added later).
Still if there's scenarios where they are still useful we want to know about them :-) Hopefully there's something better we can provide (in the future) and the external assembly can be used to bridge the gap until then.
Here's a lot of objc_msgSend P/Invokes in source code version: https://gist.github.com/rolfbjarne/981b778a99425a6e630c