Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Mapping between a XAML namespace and a CLR namespace in WinUI 3 #10021

Closed
ghost1372 opened this issue Sep 19, 2024 · 0 comments
Closed

Mapping between a XAML namespace and a CLR namespace in WinUI 3 #10021

ghost1372 opened this issue Sep 19, 2024 · 0 comments
Labels
team-Markup Issue for the Markup team

Comments

@ghost1372
Copy link
Contributor

Discussed in microsoft/WindowsAppSDK#2946

Originally posted by vladimir-stoyanov September 8, 2022
Is it possible to map between a XAML namespace and a CLR namespace in WinUI 3?

For example in WPF, the following attribute: XmlnsDefinition is placed in the AssemblyInfo.cs file in order to achieve this.

Is this achievable in WinUI 3 and if so how?

is there any plan? this is very useful for Class Library projects @Scottj1s @duncanmacmichael @michael-hawker @codendone

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-triage Issue needs to be triaged by the area owners label Sep 19, 2024
@codendone codendone transferred this issue from microsoft/WindowsAppSDK Sep 26, 2024
@codendone codendone added the team-Markup Issue for the Markup team label Sep 26, 2024
@karkarl karkarl removed the needs-triage Issue needs to be triaged by the area owners label Jan 13, 2025
@microsoft microsoft locked and limited conversation to collaborators Jan 13, 2025
@karkarl karkarl converted this issue into discussion #10293 Jan 13, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
team-Markup Issue for the Markup team
Projects
None yet
Development

No branches or pull requests

3 participants