Resolving an x:Reference in a RELEASE build picks the wrong element in some cases.

[Keflon]

Description

Repro project

https://github.com/Keflon/MauiNameBug

In a RELEASE build

Bindings to x:Name="Self" in a DataTemplate incorrectly resolve to child-controls if a child control also has x:Name="Self"

In a DEBUG build Bindings work as expected

Steps to Reproduce

1. Create a File->New MAUI app
2. Create a xaml 'child' ContentControl whose root element has x:Name="Self"
3. Create a xaml 'Parent' ContentControl whose root element also has x:Name="Self"
   1. Add a CollectionView
   2. Add a DataTemplate to the CollectionView that instantiates the 'child' ContentControl
   3. Databind something in the DataTemplate to x:Reference Self
4. Add the 'Parent' control to MainPage.xaml and populate the Parent CollectionView with some items.

In a DEBUG build, the Binding correctly resolves to an instance of the 'Parent' control
In a RELEASE build, the Binding incorrectly resolves to an instance of the 'Child' control

Version with bug

6.0.400 (current)

Last version that worked well

Unknown/Other

Affected platforms

iOS, Android, Windows

Affected platform versions

Latest

Did you find any workaround?

If you give elements an x:Name, make them unique, including any names in 3rd-party controls.

Relevant log output

No response

[StephaneDelcroix]

probably a namescoping issue. the difference between DEBUG and RELEASE is that DEBUG uses runtime xaml inflation while RELEASE compiles the XAML ahead of time.