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.
The API is documented here:
Microsoft says it's in PCLs: https://msdn.microsoft.com/en-us/library/4x7tby7x(v=vs.110).aspx
But isn't available on Xamarin.iOS.
COM features are disabled in mono runtime used in Xamarin.iOS .
The related API are not shipped in the BCL provided by XI (most of them would not work and several are not implemented in mono).
What's the use case ? the method is only 3 lines if you want to use this outside of a a COM context.
We have not received further information and will assume this is not an issue anymore. If you can still affected by this please re-open the bug and include the requested information. Thanks.
This is very much still an issue. The API is declared in a PCL profile Xamarin supports so it should be there.
The problem is that the Roslyn compiler references this function. Currently, I have to butcher the Roslyn compiler to make it work on Xamarin.
Please see this discussion from the Roslyn team - they say this is Xamarin's problem: https://github.com/dotnet/roslyn/pull/7915#discussion-diff-49557085
This is already fixed as part of the netstandard 2.0 compliance work and you should already have the API (which throws a `PlatformNotSupportedException`) if you're using XI 10.0+ 
Ah the magic of .NET Standard. Thanks!