Bug 29424 - PropertyInfo.SetValue on Nullable types not working across assemblies
Summary: PropertyInfo.SetValue on Nullable types not working across assemblies
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: XI 8.9.x (iOS 8.3)
Hardware: PC Windows
: Normal normal
Target Milestone: Untriaged
Assignee: Zoltan Varga
Depends on:
Reported: 2015-04-27 10:43 UTC by Michael Mayfield
Modified: 2015-05-05 14:49 UTC (History)
3 users (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 for Bug 29424 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Comment 1 Rolf Bjarne Kvinge [MSFT] 2015-04-28 06:09:03 UTC
Zoltan, can you have a look? It looks AOT-related (and I can reproduce with both maccore/master and 8.10)

This is the exception I get (on both armv7 and arm64): 

> Attempting to JIT compile method '(wrapper runtime-invoke) <Module>:runtime_invoke_void__this___Nullable`1<DataValue> (object,intptr,intptr,intptr)' while running with --aot-only.

It happens even if the managed linker is disabled.
Comment 2 Zoltan Varga 2015-04-29 17:43:48 UTC
This is a known limitation, it can be worked around by telling the AOT compiler to generate extra code, as it is done in the test case.