[Inflight/Candidate] Fix the Build errors when build src/Controls/samples/Controls.Sample/Maui.Controls.Sample.csproj in release.

[KarthikRajaKalaimani]

Note

Are you waiting for the changes in this PR to be merged?
It would be very helpful if you could test the resulting artifacts from this PR and let us know in a comment if this change resolves your issue. Thank you!

Issue Details:

Build error occurs when build src/Controls/samples/Controls.Sample/Maui.Controls.Sample.csproj in release.

Root Cause:

Release uses the XamlC inflator by default, which fully compiles bindings at build time. PR #35798's new TryGetRelativeSourceAncestorTypeReference logic in SetPropertiesVisitor.cs now treats AncestorType={x:Type ContentPage} as the effective source type for validation, and since SelectedItem / NavigateCommand only exist on BasePage (not ContentPage), it raises XC0045 and fails the build.

Description of Change:

The fix was applied at the source level in src/Controls/src/Build.Tasks/SetPropertiesVisitor.cs . A new tSourceRefIsAncestorTypeInferred flag now tracks whether the binding's source type came purely from AncestorType inference rather than an explicit x:DataType on the binding node. When property-path resolution against that inferred type fails, and this flag is set, the error is suppressed and the method returns false to gracefully skip TypedBinding compilation — falling back to the original reflection-based Binding , exactly as XamlC always did before PR #35798 for these ambiguous cases. This also mirrors the SourceGen inflator's existing equivalent fallback in KnownMarkups.ProvideValueForBindingExtension . Bindings with an explicit x:DataType , or where the property genuinely doesn't exist anywhere in the runtime ancestor chain, are unaffected and continue to raise XC0045 as intended, preserving PR #35798's original AOT-safety fix.

Tested the behavior in the following platforms:

• Android
• Windows
• iOS
• Mac

Reference:

N/A

Issues Fixed:

Fixes #36563

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Hey there @@KarthikRajaKalaimani! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[vishnumenon2684]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).

[vishnumenon2684]

/azp run maui-pr-uitests , maui-pr-devicetests

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
There may be pipelines that require an authorized user to comment /azp run to run.