Bug 41981 - Resolve system.drawing types to themselves when subclassing from Splat PCL to Xamarin.Mac
Summary: Resolve system.drawing types to themselves when subclassing from Splat PCL to...
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: MSBuild ()
Version: Master
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Chris Hamons
Depends on:
Reported: 2016-06-19 18:12 UTC by 999komi
Modified: 2016-06-22 16:43 UTC (History)
1 user (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 999komi 2016-06-19 18:12:55 UTC
When using the popular splat library, system.drawing types from a PCL project do resolve to the corresponding types in Xamarin.iOS, but not in Xamarin.Mac.  At a minimum, this applies to System.Drawing.Point and System.Drawing.RectangleF.

I did a writeup of this on SO here:  http://stackoverflow.com/questions/37880335/type-resolution-with-splat-library-and-xamarin-mac.

My apologies for the cross posting. I suspect this is a Xamarin issue, but it's possible the problem is with Splat or with me.
Comment 1 Chris Hamons 2016-06-20 14:13:41 UTC
Bugzilla is not a support channel. I am going to close this bug as not an issue.

For future issues of this sort, where you'd like to draw the communities attention towards a StackOverflow question, please consider opening a forum post 


However, I do agree this issue deserves an explanation, so I will answer the SO post linked.
Comment 2 999komi 2016-06-22 16:43:30 UTC
My apologies, I thought it was a Xamarin issue and was wrong.