Bug 58 - Mobile profile is missing many .NET 4.0 APIs
Summary: Mobile profile is missing many .NET 4.0 APIs
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Xamarin.iOS.dll ()
Version: 4.x
Hardware: PC Linux
: --- enhancement
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-07-25 10:06 UTC by Miguel de Icaza [MSFT]
Modified: 2015-04-16 10:44 UTC (History)
3 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Miguel de Icaza [MSFT] 2011-07-25 10:06:52 UTC
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:
* IObservable
* IObserver

Long-term, we should switch the mobile profiler to use C# 4 and the coveriant/contravariant contracts.
Comment 1 Rodrigo Kumpera 2011-07-29 12:54:09 UTC
Given JIT'd mono uses the same machinery of virtual generic methods. We might, by luck, be able to support them once variance is.
Comment 2 Miguel de Icaza [MSFT] 2011-07-29 13:11:44 UTC
Could you research the covariance/contravariance setup for AOT builds?
Comment 3 Rolf Bjarne Kvinge [MSFT] 2015-04-16 10:44:40 UTC
This was fixed a long time ago.