RuntimeBinderException when setting ((dynamic)ListView).ItemsSource in Release mode only

Question

RuntimeBinderException when setting ((dynamic)ListView).ItemsSource in Release mode only

ishebewhat 61

This issue can be reproduced easily. In a new project add a ListView (LV) and in the code-behind add the following line of code:

((dynamic)LV).ItemsSource = new List<string>();

Run in Debug mode and Release mode. In Release mode, a RuntimeBinderException will be thrown with the following message:

"Unhandled exception at 0x7B786011 (Windows.UI.Xaml.dll) in TestApp.exe: 0xC000027B: An application-internal exception has occurred (parameters: 0x06182CB0, 0x00000003)."

Then replace the line of code above with the following line of code:

LV.ItemsSource = new List<string>();

There will be no exception in either mode.

1 answer

Your answer

Answer 1

AryaDing-MSFT 2,916

Hi,
Welcome to Microsoft Q&A!

This issue might be related with the Native .NET tool chain. The Compile with .NET Native tool chain build option is activated for release builds of UWP projects, but deactivated for debug builds per default. This is a good idea in principle, because the long build time of the Native tool chain would be impossible to use for frequent test runs during development. The compiler and the .NET Native tool chain seem to produce slightly different IL code in certain scenarios, sometimes which leads to bug tickets stating that an app behaves not as specified which are not reproducible in debug mode.

In release mode, you could right click the project and select the option Properties, then disable the Compile with .NET Native tool chain in build tab, so that the code will work well. However, for more performance, I suggest you use the normal way( LV.ItemsSource = new List<string>(); ) to setting Itemsource in Debug mode.

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

ishebewhat 61 Reputation points

2021-05-11T18:50:41.417+00:00

In release mode, you could right click the project and select the option Properties, then disable the Compile with .NET Native tool chain in build tab, so that the code will work well.

But I would need to compile with .NET Native tool chain to be sure the app will run on user machines, right?
AryaDing-MSFT 2,916 Reputation points

2021-05-13T01:31:40.203+00:00

Local native compilation via the “Release” configuration will enable testing your application in an environment that is similar to what your customers will experience. As you said, disable the .NET Native tool chain may affect the the app running on users' machines. So Why don't use the normal way to set the ListView ItemSource instead of (dynamic(listView)).ItemSource?
ishebewhat 61 Reputation points

2021-05-13T01:52:01.963+00:00

We are trying to set ItemsSource for any given items control. But since we've encountered this issue, the next best option would be to conditionally cast to the control type. It will work for our purposes, but it does depend on knowing the control type at design time.
AryaDing-MSFT 2,916 Reputation points

2021-05-14T03:51:19.823+00:00

@ishebewhat As long as a control inherits from ItemsControl, you could use ItemsSouce property set data source directly. If you don't know the control type, you could convert it to ItemsControl type.
ishebewhat 61 Reputation points

2021-05-14T06:20:18.553+00:00

There are built-in controls with an ItemSource property that don't inherit from ItemsControl. So we would still need a condition statement based on this, as an example. But the fact that this is even an issue is concerning. How could setting an object cause this exception? From what I understand, this exception is an actual binding failure. As opposed to the RuntimeBinderInternalCompilerException.
AryaDing-MSFT 2,916 Reputation points

2021-05-20T01:37:41.857+00:00

@ishebewhat My error message is “Microsoft.CSharp.RuntimeBinder.RuntimeBinderException: ''Windows.UI.Xaml.Controls.ListView' does not contain a definition for 'ItemsSource''”. The dynamic keyword has various corner cases that don’t run super well on .NET Native. Generally, The general idea is that the dynamic keyword causes a great deal of machinery to wander through APIs and some pieces of the framework don't have the proper hinting to say "This isn't a thing you need to reflect on." Because our compiler analysis says you won't need this type at runtime but this particular component does, we end up throwing this exception.

Share via

RuntimeBinderException when setting ((dynamic)ListView).ItemsSource in Release mode only

1 answer

Your answer