Bug 4562 - Type representation
Summary: Type representation
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS add-in ()
Version: 2.9.x
Hardware: Macintosh Mac OS
: Highest blocker
Target Milestone: ---
Assignee: Mike Krüger
URL:
: 4532 ()
Depends on:
Blocks:
 
Reported: 2012-04-20 11:11 UTC by Mike Krüger
Modified: 2012-04-23 07:27 UTC (History)
5 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 Mike Krüger 2012-04-20 11:11:30 UTC
In the MonoMac addin the type mapping is done with a string (FullName).

The FullName doesn't really represent a type.
Some issues with that:

+ Type parameters
+ Inner types

The type system uses a TypeReferences system for looking up types - the monomac addin should use that as well - it solves all the issues of looking up types.

The old DOM just tried to ignore the type parameters and gave back the first thing that could possible match. That his is a no-go should be clear.

The LookupType method tries to mimic the old (wrong) behaviour but should never be used. For having a better string representation ReflectionNames could be used - but IMO just using TypeReferences are a better solution.
Comment 1 Mike Krüger 2012-04-20 11:14:52 UTC
*** Bug 4532 has been marked as a duplicate of this bug. ***
Comment 7 Jeffrey Stedfast 2012-04-20 17:51:42 UTC
*** Bug 4467 has been marked as a duplicate of this bug. ***
Comment 8 Mike Krüger 2012-04-21 04:50:34 UTC
I don't think it's something that has to do with #4467.
Comment 9 Mike Krüger 2012-04-23 07:27:29 UTC
Should work in more abstract cases now / fixed.

(I took the approach with reflection names.)