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 MOBILE profile is supposed to be the .NET 4.0 API, minus anything that brings the System.Configuration bloat or things that would introduce big dependencies that are hard to link out.
There is a problem with the use of covariant and contravariant interfaces now, so adopting everything as a whole might be complicated. But there are a handful of APIs that are worth brining step-by-step.
We need to audit the library to ensure that all of the new 4.0 stuff makes it into our mobile products.
A few simple things that we are missing:
From a customer feature request:
Long-term, we should switch the mobile profiler to use C# 4 and the coveriant/contravariant contracts.
Given JIT'd mono uses the same machinery of virtual generic methods. We might, by luck, be able to support them once variance is.
Could you research the covariance/contravariance setup for AOT builds?
This was fixed a long time ago.