-
Notifications
You must be signed in to change notification settings - Fork 677
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
C++/WinRT - InitializeComponent issue with XAML derived class in sub-namespace #7600
Comments
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
@bpulliam @gabbybilka Please re-open the issue. |
Hi, does this only repro in UWP? Are you using System Xaml / WinUI2, or are you using WinAppSDK / WinUI3? (looks like the link to your repro app is broken). Thanks! |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 7 days of this comment. |
Describe the bug
Original issue: microsoft/cppwinrt#1169.
Minimal repro: https://github.com/Jaiganeshkumaran/XamlIssueRepro.Cpp.
Having a XAML class deriving from another control like Button, rather than Page/UserControl, fails to compile, saying InitializeComponent is not a member. I've noticed that this only occurs when the type is inside a sub-namespace, that is sub-namespace of the project's root namespace.
Steps to reproduce the bug
Expected behavior
No response
Screenshots
No response
NuGet package version
No response
Windows app type
Device form factor
No response
Windows version
Windows 11 (21H2): Build 22000
Additional context
The text was updated successfully, but these errors were encountered: