Skip to content

Add missing App.InitializeComponent() call in WinUI sample#625

Open
yeelam-gordon wants to merge 1 commit intomainfrom
fix/61791038-winui-missing-initcomponent
Open

Add missing App.InitializeComponent() call in WinUI sample#625
yeelam-gordon wants to merge 1 commit intomainfrom
fix/61791038-winui-missing-initcomponent

Conversation

@yeelam-gordon
Copy link
Copy Markdown
Contributor

Fixes ADO #61791038

The WinUI cs-winui sample was missing the App.InitializeComponent() call, which could cause XAML resources to not load properly.

Without InitializeComponent(), XAML resources may not load properly.
Fixes ADO #61791038

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR fixes the WinUI 3 WindowsML C# sample startup initialization by adding the missing App.InitializeComponent() call so that App.xaml resources (e.g., merged dictionaries like XamlControlsResources) are properly loaded at app startup.

Changes:

  • Add an App() constructor that calls this.InitializeComponent() in the WinUI cs-winui sample.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@yeelam-gordon yeelam-gordon requested a review from timkur April 14, 2026 23:00
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