Bug 14608 - TypeInfo is not correct for a generic type
Summary: TypeInfo is not correct for a generic type
Status: RESOLVED DUPLICATE of bug 14168
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 4.8.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2013-09-10 12:47 UTC by Jon Goldberger [MSFT]
Modified: 2013-09-12 18:07 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Test project (468.77 KB, application/zip)
2013-09-10 12:47 UTC, Jon Goldberger [MSFT]
Details


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 DUPLICATE of bug 14168

Description Jon Goldberger [MSFT] 2013-09-10 12:47:53 UTC
Created attachment 4825 [details]
Test project

I'm working with Xamarin.Android 4.8.

Assume a test like the following:

[Test]
public void TestTypeInfo() {
  var ti = typeof(List<string>).GetTypeInfo();
  Assert.IsTrue(ti.IsGenericType);
  Assert.IsTrue(ti.GenericTypeArguments.Length == 1);
}
This should pass, as it does in standard .NET, but fails in Xamarin. In Xamarin, the TypeInfo returned is not correct for generic types.

Any plans to fix this?
Comment 2 Jonathan Pryor 2013-09-12 18:07:21 UTC

*** This bug has been marked as a duplicate of bug 14168 ***