Skip to content

[release/9.0.1xx-sr6] Avoid qualified name in x:Type binding for Blazor Hybrid template #29011

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

github-actions[bot]
Copy link
Contributor

Backport of #29005 to release/9.0.1xx-sr6

/cc @mattleibow @BretJohnson

Use an explicit XML namespace for Component, avoiding use
qualified name syntax in the x:Type binding. Qualified names
(like `local:Components.Routes`) aren't currently supported by
XAML Hot Reload, producing the error
"Nested types are not supported: Components.Routes"
and causing XAML Hot Reload to not work. This support
is coming in a future VS update, but for now it's best to avoid
using of the qualified name syntax in our templates, to keep
things broadly compatible and working for new users. We
don't use qualified names in XAML bindings anywhere else
in MAUI XAML templates; this is the last occurrence.

Fixes #20669
@github-actions github-actions bot requested a review from a team as a code owner April 15, 2025 21:26
@rmarinho
Copy link
Member

/azp run

Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@rmarinho rmarinho merged commit e29347f into release/9.0.1xx-sr6 Apr 22, 2025
7 checks passed
@rmarinho rmarinho deleted the backport/pr-29005-to-release/9.0.1xx-sr6 branch April 22, 2025 09:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants